Re: ref name troubles, was Re: [PATCH v2] Introduce %<branch> as shortcut to the tracked branch
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 20, 2009, 06:57 UTC
- Message-ID
- <7vprgc4r6h.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <20090320060545.GB27008@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 11 quoted lines
> On Thu, Mar 19, 2009 at 05:40:29PM -0700, Shawn O. Pearce wrote:
>
>> So yea, you can create a branch named "foo@{1}".
>
> But you can't actually refer to it:
>
> $ git branch foo@{1}
> $ git show foo@{1} --
> fatal: bad revision 'foo@{1}'
>
> which implies that nobody is actually using it for anything.I think you are right. It is just "git branch" and perhaps "git update-ref" are too loose in enforcing what can be created.