Re: [PATCH] Teach revision walker about reflog ranges

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 30, 2007, 00:16 UTC
Message-ID: <7vve6h9gvz.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <Pine.LNX.4.64.0712300000170.14355@wbgn129.biozentrum.uni-wuerzburg.de>

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

Show 7 quoted lines

> Now you can ask for a revision range
>
> 	master@{2.weeks.ago..1.day.ago}
>
> or even something like
>
> 	HEAD@{20..yesterday}

You can _ask_ all you want, but it is not clear what it does from this description. I guess you are rewriting master@{A..B} to master@{A}..master@{B}, but that is not clear from the commit log nor documentation (did I even see a documentation patch?).

Also, I am not convinced that the rewrite gives the semantics the users naturally expect from @{A..B}. I would even suspect that people would expect "git log master@{0..2}" to behave more like "git show master@{0} master@{1} master@{2}".