From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: `git-rev-parse master` not referred to by any ref?
Date: Sun, 26 Aug 2007 18:36:10 -0400 [thread overview]
Message-ID: <20070826223610.GB9116@fieldses.org> (raw)
In-Reply-To: <7vir72ng1n.fsf@gitster.siamese.dyndns.org>
On Sun, Aug 26, 2007 at 02:26:28PM -0700, Junio C Hamano wrote:
> It _might_ make it safer to refuse creating anything outside
> refs/ if the name does not contain or ends with "HEAD" (or
> perhaps names that have chars outside "[_A-Z]"), but that would
> restrict future tools that might want to have HEAD-like files,
> so I am a bit hesitant.
Sure.
I would have recovered faster if I'd known had a simple way to get a
list of all the refs that git-rev-parse finds. Is there an easy way? I
assume "find .git -name .." will miss packed refs. Both git-show-ref
and git-for-each-ref seem to ignore top-level references.
Maybe the "refname 'master' is ambiguous" warning could be modified to
list the choices? I don't know if that would be overkill.
--b.
prev parent reply other threads:[~2007-08-26 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 13:45 `git-rev-parse master` not referred to by any ref? J. Bruce Fields
2007-08-26 13:52 ` J. Bruce Fields
2007-08-26 14:06 ` J. Bruce Fields
2007-08-26 21:26 ` Junio C Hamano
2007-08-26 22:28 ` Shawn O. Pearce
2007-08-26 22:36 ` J. Bruce Fields [this message]
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=20070826223610.GB9116@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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