Re: git log -g bizarre behaviour

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 2, 2016, 19:32 UTC
Message-ID: <xmqqsi1asyai.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <1454401738.32711.7.camel@kaarsemaker.net>

Dennis Kaarsemaker <dennis@kaarsemaker.net> writes:

Show 19 quoted lines

> On ma, 2016-02-01 at 15:37 -0800, Junio C Hamano wrote:
>
>> Do you mean
>> 
>> 	$ git checkout -b testing
>>         $ rm -f .git/logs/refs/heads/testing
>>         $ git log -g testing
>> 
>> will be changed from a silent no-op to an abort with error?
>> 
>> I do not see a need for such a change--does that count as an
>> objection?
>
> No, I'd like to change:
>
> $ ls .git/logs/refs/tags/v2.7.0
> ls: cannot access .git/logs/refs/tags/v2.7.0: No such file or directory
> $ git (log -g|reflog) v2.7.0
> From the bizarre behaviour above to a silent noop.

When there is nothing to show, we do not show anything, and that is just like "git log v2.7.0..v2.7.0" is silent.

I do not find the silence bizarre at all.