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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 20, 2007, 01:19 UTC
Message-ID: <Pine.LNX.4.63.0701200218290.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vr6tqbjt8.fsf@assigned-by-dhcp.cox.net>

Hi,

On Fri, 19 Jan 2007, Junio C Hamano wrote:

Show 23 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Fri, 19 Jan 2007, Junio C Hamano wrote:
> >
> >> I still am having a hard time trying to explain what these
> >> commands would do, and why they might be useful:
> >> 
> >> 	git-log --walk-reflogs master..next
> >
> > I had less problems explaining that when walking fell back to walking the 
> > parents.
> >
> > It could even make sense to...
> 
> (meaning that is not what the code does...)
> 
> > Of course, you could always say: if you ask for strange things, you will 
> > get strange things.
> 
> But if you have to say that, doesn't it suggest that accepting
> the option --walk-reflogs when you have anything other than one
> single positive commit in revs.pending leads to end user
> confusion?

How about failing if there are _uninteresting_ commits? So,

	git log --walk-reflogs next master

still works?

Ciao, Dscho