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

git init --bare versus git --bare init

From
OHOliver Hoffmann <oliverhoffmann32@googlemail.com>
Date
May 8, 2010, 10:38 UTC
Message-ID
<201005081238.14156.oliverhoffmann32@googlemail.com>
Hi Git Folk,

If one accidentally writes "git --bare init <dir>" instead of "git init --bare <dir>" an appended directory argument is ignored and $CUR_DIR or the working directory will be used:

> pwd
/tmp/foo
> git --bare init /tmp/bar
Initialized empty Git repository in /tmp/foo/
> git init --bare /tmp/bar
Initialized empty Git repository in /tmp/bar/
... but both should probably be initialized in /tmp/bar/

Greetings, Oliver Hoffmann

Next: Jeff King
Message 1 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.