Re: [PATCH 3/3] show-branch --reflog: show the reflog message at the top.

From: Junio C Hamano <junkio@cox.net>
Date: Jan 20, 2007, 01:32 UTC
Message-ID: <7v4pqmbhzg.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0701200218290.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 5 quoted lines

> How about failing if there are _uninteresting_ commits? So,
>
> 	git log --walk-reflogs next master
>
> still works?

That feels like a good way to deal with it. I think people may also appreciate timestamps on Reflog headers you add to the output.

That change makes

	$ git log --walk-reflogs master..next
        fatal: No reflogs found for 'master..next'

a non issue, for one thing.

Unfortunately,

	$ git log --walk-reflogs ^master next

is not something I can read and make heads or tails of it. So I'll try something smaller:

	$ git log --walk-reflogs ^master jc/show-reflog

shows only three commits (the same as without --walk-reflogs), although I have tons of rewinds and rebases. There is something broken, or perhaps the semantics of --walk-reflogs does not match what humans would expect when interacting with revision limiting. This would also become an non-issue if we do not allow negative ones.