Re: [PATCH] interpret_nth_last_branch(): avoid traversing the reflogs twice
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 20, 2009, 08:35 UTC
- Message-ID
- <7v4ozul6hi.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.0901191331590.3586@pacific.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> This, together with a removal of the hard-coded limit of 16 could be > squashed with this patch:
Yeah, I think that makes very much sense, not because 16 is too small, but because it does not make sense to keep track of all 16 when you asked for the last (or the second from the last) event.
Thanks for a free sanity ;-)