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

Re: [PATCH] Do not allow git-init-db to be called twice in the same directory

From
Junio C Hamano <junkio@cox.net>
Date
Dec 27, 2005, 01:18 UTC
Message-ID
<7vbqz3ibhn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0512270053030.14928@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> t5300 is also adapted, since it relies heavily on init-db not complaining 
> when $GIT_DIR already exists.

I think it tries not to overwrite things that are already there and is meant to be safe to run in an already populated repository; e.g. you should be able to use it to pick up newly added templates.

Is there a particular reason running the current init-db twice is undesirable?

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 2 of 5 in “Do not allow git-init-db to be called twice in the same directory”
  1. Do not allow git-init-db to be called twice in the same directoryJohannes Schindelin, Dec 26, 2005
  2. Junio C HamanoDec 27, 2005
  3. Johannes SchindelinDec 27, 2005
  4. Junio C HamanoDec 27, 2005
  5. Johannes SchindelinDec 27, 2005

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.