Re: [RFC/PATCH 10/11] branch.c: use 'ref-filter' APIs
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Aug 19, 2015, 15:49 UTC
- Message-ID
- <vpq37zf2s84.fsf@anie.imag.fr>
- In-Reply-To
- <CAOLa=ZTNv7bRMZL_yAGSKxDyBPUBuMQKsybQBg3sKbLzM=m0YQ@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 8 quoted lines
> On Thu, Jul 30, 2015 at 12:59 PM, Matthieu Moy > <Matthieu.Moy@grenoble-inp.fr> wrote: > >> IIRC, historicaly Git allowed some weirdly named refs which made some >> commands ambiguous (e.g. a branch named after an option like '-d'). >> We're forbidding their creation so people shouldn't have any, but we >> it's important to continue showing them in case some people have old >> bad-named branches lying around.
[...]
Show 7 quoted lines
> Agreed. But then again the warning tells about the broken ref, as in it's name > So I think It's ok? > > for e.g. t1430 : > [trash directory.t1430-bad-ref-name] ../../git branch > warning: ignoring ref with broken name refs/heads/broken...ref > * master
[ Late answer, I'm still catching up with my holiday's emails ;-) ]
OK, the warning gives a different interface but it seems as good as the old one.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/