Junio C Hamano <gits...@pobox.com> writes:
> y...@google.com writes:
>> From: Martin von Zweigbergk <martin.von.zweigbe...@gmail.com>
>> When 'git cherry-pick' and 'git revert' are used with ranges such as
>> 'git cherry-pick A..B', the order of the commits to pick are
>> determined by the default date-based sorting. If a commit has a commit
>> date before the commit date of its parent, it will therfore be applied
>> before its parent.
> Is that what --topo-order really means?
And it turns out that the documentation is crappy. Perhaps
something like this, but an illustration may not hurt.
Documentation/rev-list-options.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/rev-list-options.txt
index d9b2b5b..c147117 100644
@@ -579,9 +579,10 @@ Commit Ordering
By default, the commits are shown in reverse chronological order.
- This option makes them appear in topological order (i.e.
- descendant commits are shown before their parents).
+ This option makes them appear in topological order. Even
+ without this option, descendant commits are shown before
+ their parents, but this tries to avoid showing commits on
+ multiple lines of history intermixed.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html