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

Re: importance of .git extension for bare repos

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Feb 16, 2012, 01:38 UTC
Message-ID
<CALUzUxqEirjnCBHt28dwcgTBqC+u0wydNsnVR1rgyGG0-R_M1w@mail.gmail.com>
In-Reply-To
<jhhkn8$a0t$1@dough.gmane.org>

I don't believe its significant to git itself, it's just a convention for us humans.

-- 
Cheers,
Ray Chuan


On Thu, Feb 16, 2012 at 9:04 AM, Neal Kreitzinger <neal@rsss.com> wrote:
> I have a user who has created bare repos without naming them with the .git
> extension.  As a result, the file paths are MYBARE/config instead of
> MYBARE.git/config, etc.  Is this a supported naming convention for bare
> repos in git.git, or is it going to have some problems?
>
> v/r,
> neal
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous: Neal KreitzingerNext: Jeff King
Message 2 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.