From: "Neal Kreitzinger" <neal@rsss.com>
To: git@vger.kernel.org
Subject: importance of .git extension for bare repos
Date: Wed, 15 Feb 2012 19:04:40 -0600 [thread overview]
Message-ID: <jhhkn8$a0t$1@dough.gmane.org> (raw)
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
next reply other threads:[~2012-02-16 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 1:04 Neal Kreitzinger [this message]
2012-02-16 1:38 ` importance of .git extension for bare repos Tay Ray Chuan
2012-02-16 2:30 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jhhkn8$a0t$1@dough.gmane.org' \
--to=neal@rsss.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).