Re: [PATCH] interpret_nth_last_branch(): avoid traversing the reflogs twice
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 17, 2009, 19:13 UTC
- Message-ID
- <7vljt97nld.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.0901171602340.3586@pacific.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Instead of traversing them twice, we just build a list of branch switches, > pick the one we're interested in, and free the list again.
Isn't the code keeping them all in core, or am I reading the patch wrong?
If you know that you are interested in the nth-from-the-last switch, and if you are reading from the beginning, you would need to keep at most n last switches you have seen in core, wouldn't you?