Files
git/Documentation
Martin von Zweigbergk ca92e59e30 teach log --no-walk=unsorted, which avoids sorting
When 'git log' is passed the --no-walk option, no revision walk takes
place, naturally. Perhaps somewhat surprisingly, however, the provided
revisions still get sorted by commit date. So e.g 'git log --no-walk
HEAD HEAD~1' and 'git log --no-walk HEAD~1 HEAD' give the same result
(unless the two revisions share the commit date, in which case they
will retain the order given on the command line). As the commit that
introduced --no-walk (8e64006 (Teach revision machinery about
--no-walk, 2007-07-24)) points out, the sorting is intentional, to
allow things like

 git log --abbrev-commit --pretty=oneline --decorate --all --no-walk

to show all refs in order by commit date.

But there are also other cases where the sorting is not wanted, such
as

 <command producing revisions in order> |
       git log --oneline --no-walk --stdin

To accomodate both cases, leave the decision of whether or not to sort
up to the caller, by allowing --no-walk={sorted,unsorted}, defaulting
to 'sorted' for backward-compatibility reasons.

Signed-off-by: Martin von Zweigbergk <martinvonz@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-08-30 12:26:50 -07:00
..
2012-03-28 08:47:23 -07:00
2012-06-17 14:07:15 -07:00
2011-08-08 09:30:12 -07:00
2012-04-20 15:49:16 -07:00
2012-05-03 15:13:31 -07:00
2012-03-05 11:32:19 -08:00
2011-12-12 11:52:31 -08:00
2012-05-07 13:28:34 -07:00
2011-09-06 11:42:12 -07:00
2011-05-19 10:55:54 -07:00
2012-04-27 09:26:39 -07:00
2012-06-17 14:07:15 -07:00
2012-06-08 08:32:20 -07:00