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, 00:42 UTC
Message-ID: <Pine.LNX.4.63.0701200135500.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7v4pqmczqa.fsf@assigned-by-dhcp.cox.net>

Hi,

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 walk reflogs instead of parents _only_ for interesting commits (i.e. "next" in your example, but not "master"), so that you can ask for commits made to a certain in your local repository, which are not (yet) in some other branch.

Which would include commits which were ammended (and thus are no longer in the ancestry of the branch).

Of course, you could always say: if you ask for strange things, you will get strange things.

> 	git-log --walk-reflogs master -- Documentation/

Ah, but that is way easier!

For example: I _know_ that something worked some time ago, and it was probably in git.c. So ask "git-log --walk-reflogs -- git.c", and you will soon find out where to start bisecting.

> On the other hand I can understand why this might be useful:
> 
> 	git-log --walk-reflogs master

I like it already. But of course, I also like your patch saying "3 days ago" instead of a date.

Ciao, Dscho