Re: [PATCH v2 1/3] teach log --no-walk=unsorted, which avoids sorting

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 29, 2012, 17:42 UTC
Message-ID: <7vharlwq5l.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAPBPrnstykXxTEH56YFDqU2XW+o8WRKBN6=QOTpLJ1jRU7DXCA@mail.gmail.com>

Dan Johnson <computerdruid@gmail.com> writes:

> Perhaps I am missing something from an earlier discussion, but it is

  http://thread.gmane.org/gmane.comp.version-control.git/203259/focus=203344

Show 5 quoted lines

> not obvious to me why this is an option to the no-walk behavior and
> not something like --sorted/--unsorted as a separate option.
>
> In other words, I don't understand why you always want to sort if you
> are doing revision walking.

When you have more than one starting points to dig the history from (e.g. "git log foo bar baz"), you would want to start digging from the newer ones, as that would help you find the fork points of the branches involved more efficiently. But you need to follow the previous discussion if you want to understand implications around sorting.