projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d0f1ea6) | patch
rev-list docs: clarify --topo-order description
authorJunio C Hamano <gitster@pobox.com>
Wed, 15 Aug 2012 20:02:48 +0000 (13:02 -0700)
committerJunio C Hamano <gitster@pobox.com>
Wed, 15 Aug 2012 20:04:20 +0000 (13:04 -0700)
commit3f0350ccd5378520d472fd5e5a8a9fb21db50762
tree1934fce04bd4009a14ccd202add23431e093c293tree | snapshot
parentd0f1ea6003d97e63110fa7d50bb07f546a909b6ecommit | diff
rev-list docs: clarify --topo-order description

It was unclear what "--topo-order" was really about in the
documentation.  It is not just about "children before parent", but
also about "don't mix lineages".

Reword the description for both "--date-order" and "--topo-order",
and add an illustration to it.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/rev-list-options.txt diff | blob | history
Git—the stupid content tracker