Skip to content

Commit e301bfe

Browse files
spearcegitster
authored andcommitted
Fix new-workdir (again) to work on bare repositories
My day-job workflow involves using multiple workdirs attached to a bunch of bare repositories. Such repositories are stored inside of a directory called "foo.git", which means `git rev-parse --git-dir` will return "." and not ".git". Under such conditions new-workdir was getting confused about where the Git repository it was supplied is actually located. If we get "." for the result of --git-dir query it means we should use the user supplied path as-is, and not attempt to perform any magic on it, as the path is directly to the repository. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent a475e80 commit e301bfe

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

contrib/workdir/git-new-workdir

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,14 @@ git_dir=$(cd "$orig_git" 2>/dev/null &&
2424
git rev-parse --git-dir 2>/dev/null) ||
2525
die "\"$orig_git\" is not a git repository!"
2626

27-
if test "$git_dir" = ".git"
28-
then
27+
case "$git_dir" in
28+
.git)
2929
git_dir="$orig_git/.git"
30-
fi
30+
;;
31+
.)
32+
git_dir=$orig_git
33+
;;
34+
esac
3135

3236
# don't link to a workdir
3337
if test -L "$git_dir/config"

0 commit comments

Comments
 (0)