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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

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

> Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]