{"thread":{"id":"29641","subject":"importance of .git extension for bare repos","startedAt":"2012-02-16T01:04:40Z","lastAt":"2012-02-16T02:30:27Z","messageCount":3,"participants":["Neal Kreitzinger","Tay Ray Chuan","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"184801","messageId":"jhhkn8$a0t$1@dough.gmane.org","threadId":"29641","inReplyTo":null,"subject":"importance of .git extension for bare repos","fromName":"Neal Kreitzinger","fromEmail":"neal@rsss.com","sentAt":"2012-02-16T01:04:40Z","receivedAt":"2012-02-16T01:04:40Z","isPatch":false,"sender":{"key":"neal@rsss.com","avatar":null},"body":"I have a user who has created bare repos without naming them with the .git \nextension.  As a result, the file paths are MYBARE/config instead of \nMYBARE.git/config, etc.  Is this a supported naming convention for bare \nrepos in git.git, or is it going to have some problems?\n\nv/r,\nneal \n"},{"id":"184802","messageId":"CALUzUxqEirjnCBHt28dwcgTBqC+u0wydNsnVR1rgyGG0-R_M1w@mail.gmail.com","threadId":"29641","inReplyTo":"jhhkn8$a0t$1@dough.gmane.org","subject":"Re: importance of .git extension for bare repos","fromName":"Tay Ray Chuan","fromEmail":"rctay89@gmail.com","sentAt":"2012-02-16T01:38:08Z","receivedAt":"2012-02-16T01:38:08Z","isPatch":false,"sender":{"key":"rctay89@gmail.com","avatar":"https://avatars.githubusercontent.com/u/61553?v=4"},"body":"I don't believe its significant to git itself, it's just a convention\nfor us humans.\n\n-- \nCheers,\nRay Chuan\n\n\nOn Thu, Feb 16, 2012 at 9:04 AM, Neal Kreitzinger <neal@rsss.com> wrote:\n> I have a user who has created bare repos without naming them with the .git\n> extension.  As a result, the file paths are MYBARE/config instead of\n> MYBARE.git/config, etc.  Is this a supported naming convention for bare\n> repos in git.git, or is it going to have some problems?\n>\n> v/r,\n> neal\n>\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"},{"id":"184803","messageId":"20120216023027.GA26518@sigill.intra.peff.net","threadId":"29641","inReplyTo":"CALUzUxqEirjnCBHt28dwcgTBqC+u0wydNsnVR1rgyGG0-R_M1w@mail.gmail.com","subject":"Re: importance of .git extension for bare repos","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2012-02-16T02:30:27Z","receivedAt":"2012-02-16T02:30:27Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Feb 16, 2012 at 09:38:08AM +0800, Tay Ray Chuan wrote:\n\n> I don't believe its significant to git itself, it's just a convention\n> for us humans.\n\nThat's not entirely true. If you try to access a repository by name\n(e.g., \"git clone foo\", \"git fetch foo\"), git will look for \"foo.git\".\nThis magic lookup works for local repositories, and for remote\nrepositories served over ssh or by git-daemon. I think it should also\nwork for smart-http, but I didn't check. It doesn't work for dumb http\n(because it would involve making several exploratory http requests).\n\n-Peff\n"}]}