Martin von Zweigbergk <martin.von.zweigbergk@xxxxxxxxx> writes: >> diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt >> index 6a4b635..dc501ee 100644 >> --- a/Documentation/rev-list-options.txt >> +++ b/Documentation/rev-list-options.txt >> @@ -579,15 +579,32 @@ Commit Ordering >> By default, the commits are shown in reverse chronological order. > > It seems likely that those reading the above sentence will continue on > to read about --topo-order, but still, do you think the "descendant > commits are shown before parents" part belong here instead? I do not think so. When you are not limited (i.e. limit_list() is not called), you could do something like "git rev-list 4 5" in a history like this: --1---5---2---3---4 and get end up getting "5 4 3 2 1", and "2" certainly doesn't get shown before "5" does. In your series where cherry-pick runs prepare_revision_walk() and makes the outcome sort in reverse, the list has to be limited, so the above is a non-issue, but in the context of this document, we cannot assume that. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html