# importance of .git extension for bare repos

3 messages from 2012-02-16 to 2012-02-16. Participants: Neal Kreitzinger, Tay Ray Chuan, Jeff King.
Thread: https://gitlist.dev/t/29641

## Neal Kreitzinger, 2012-02-16 01:04

Subject: importance of .git extension for bare repos
Message-ID: <jhhkn8$a0t$1@dough.gmane.org>
URL: https://gitlist.dev/e/jhhkn8%24a0t%241%40dough.gmane.org

```
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 

```

## Tay Ray Chuan, 2012-02-16 01:38

Subject: Re: importance of .git extension for bare repos
Message-ID: <CALUzUxqEirjnCBHt28dwcgTBqC+u0wydNsnVR1rgyGG0-R_M1w@mail.gmail.com>
URL: https://gitlist.dev/e/CALUzUxqEirjnCBHt28dwcgTBqC%2Bu0wydNsnVR1rgyGG0-R_M1w%40mail.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

```

## Jeff King, 2012-02-16 02:30

Subject: Re: importance of .git extension for bare repos
Message-ID: <20120216023027.GA26518@sigill.intra.peff.net>
URL: https://gitlist.dev/e/20120216023027.GA26518%40sigill.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

```