From: Karthik Nayak <karthik.188@gmail.com>
Date: Wed, 19 Aug 2015 15:52:50 GMT
Subject: Re: [RFC/PATCH 10/11] branch.c: use 'ref-filter' APIs
Message-ID: <CAOLa=ZQqewSJtf-4WWY=gr3e0sU5TyBK3gcy-b4YXdS8jXCDZg@mail.gmail.com>
In-Reply-To: <vpq37zf2s84.fsf@anie.imag.fr>

On Wed, Aug 19, 2015 at 9:19 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> 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.
> [...]
>> 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.
>

Ah! yes :)

-- 
Regards,
Karthik Nayak