git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] handle "git --bare init <dir>" properly

From
Jeff King <peff@peff.net>
Date
May 10, 2010, 09:42 UTC
Message-ID
<20100510094206.GA30869@coredump.intra.peff.net>
In-Reply-To
<201005081238.14156.oliverhoffmann32@googlemail.com>

If we know we are creating a bare repository, we use setenv to set the GIT_DIR directory to the current directory (either where we already were, or one we created and chdir'd into with "git init --bare <dir>").

However, with "git --bare init <dir>" (note the --bare as a git wrapper option), the setup code actually sets GIT_DIR for us, but it uses the wrong, original cwd when a directory is given. Because our setenv does not use the overwrite flag, it is ignored.

We need to set the overwrite flag, but only when we are given a directory on the command line. That still allows:

  GIT_DIR=foo.git git init --bare
to work. The behavior is changed for:
  GIT_DIR=foo.git git init --bare bar.git

which used to create the repository in foo.git, but now will use bar.git. This is more sane, as command line options should generally override the environment.

Noticed by Oliver Hoffmann.
Signed-off-by: Jeff King <peff@peff.net>
---
Thanks for the bug report, Oliver.
 builtin/init-db.c |    2 +-
 t/t0001-init.sh   |   14 ++++++++++++++
 2 files changed, 15 insertions(+), 1 deletions(-)
diff --git a/builtin/init-db.c b/builtin/init-db.c
index edc40ff..0271285 100644
--- a/builtin/init-db.c
+++ b/builtin/init-db.c
@@ -463,7 +463,7 @@ int cmd_init_db(int argc, const char **argv, const char *prefix)
 		static char git_dir[PATH_MAX+1];
 
 		setenv(GIT_DIR_ENVIRONMENT,
-			getcwd(git_dir, sizeof(git_dir)), 0);
+			getcwd(git_dir, sizeof(git_dir)), argc > 0);
 	}
 
 	if (init_shared_repository != -1)
diff --git a/t/t0001-init.sh b/t/t0001-init.sh
index 6757734..7c0a698 100755
--- a/t/t0001-init.sh
+++ b/t/t0001-init.sh
@@ -310,4 +310,18 @@ test_expect_success POSIXPERM 'init notices EPERM' '
 	)
 '
 
+test_expect_success 'init creates a new bare directory with global --bare' '
+	rm -rf newdir &&
+	git --bare init newdir &&
+	test -d newdir/refs
+'
+
+test_expect_success 'init prefers command line to GIT_DIR' '
+	rm -rf newdir &&
+	mkdir otherdir &&
+	GIT_DIR=otherdir git --bare init newdir &&
+	test -d newdir/refs &&
+	! test -d otherdir/refs
+'
+
 test_done
-- 
1.7.1.248.gf52fc.dirty
Previous: Oliver Hoffmann
Message 2 of 2 in “git init --bare versus git --bare init”
  1. Oliver HoffmannMay 8, 2010
  2. handle "git --bare init <dir>" properlyJeff King, May 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.