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

Re: importance of .git extension for bare repos

From
Jeff King <peff@peff.net>
Date
Feb 16, 2012, 02:30 UTC
Message-ID
<20120216023027.GA26518@sigill.intra.peff.net>
In-Reply-To
<CALUzUxqEirjnCBHt28dwcgTBqC+u0wydNsnVR1rgyGG0-R_M1w@mail.gmail.com>
On Thu, Feb 16, 2012 at 09:38:08AM +0800, Tay Ray Chuan wrote:
> I don't believe its significant to git itself, it's just a convention
> for us humans.

That's not entirely true. If you try to access a repository by name (e.g., "git clone foo", "git fetch foo"), git will look for "foo.git". This magic lookup works for local repositories, and for remote repositories served over ssh or by git-daemon. I think it should also work for smart-http, but I didn't check. It doesn't work for dumb http (because it would involve making several exploratory http requests).

-Peff
Previous: Tay Ray Chuan
Message 3 of 3 in “importance of .git extension for bare repos”
  1. Neal KreitzingerFeb 16, 2012
  2. Tay Ray ChuanFeb 16, 2012
  3. Jeff KingFeb 16, 2012

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.