Re: [PATCH] --walk-reflogs: disallow uninteresting commits

From

Junio C Hamano <junkio@cox.net>

Date

Jan 20, 2007, 07:21 UTC

Message-ID

<7v64b29naa.fsf@assigned-by-dhcp.cox.net>

In-Reply-To

<Pine.LNX.4.63.0701200325380.22628@wbgn013.biozentrum.uni-wuerzburg.de>

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

> 	> I think people may also appreciate timestamps on Reflog headers 
> 	> you add to the output.
>
> 	At the moment, if you ask for @{1} (or leave it out), you will see 
> 	them enumerated by number. If you ask for @{now}, you will see 
> 	them identified by date...

By the way, I haven't looked into it, but does this ring a bell?

    $ git-log --walk-reflogs -1 --pretty=s master@{1.day}
    commit 72fe6a59890870ed9c3e9e1e6381fc0d7ba75fe4
    Reflog: master@{Thu, 1 Jan 1970 00:00:00 +0000} ((null))
    Reflog message: (null)Author: Junio C Hamano <junkio@cox.net>

        Documentation: Generate command lists.

---

diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
index 86c94e7..fcc540b 100644
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -190,6 +190,21 @@ limiting may be applied.
 	In addition to the '<commit>' listed on the command
 	line, read them from the standard input.
 
+--walk-reflogs::
+
+	Instead of walking the commit ancestry chain, walk
+	reflog entries from the most recent one to older ones.
+	When this option is used you cannot specify commits to
+	exclude (that is, '{caret}commit', 'commit1..commit2',
+	nor 'commit1...commit2' notations cannot be used).
++
+With '\--pretty' format other than oneline (for obvious reasons),
+this causes the output to have two extra lines of information
+taken from the reflog.  By default, 'commit@{Nth}' notation is
+used in the output.  When the starting commit is specified as
+'commit@{now}', output also uses 'commit@{timestamp}' notation
+instead.
+
 --merge::
 
 	After a failed merge, show refs that touch files having a