aboutsummaryrefslogtreecommitdiff
path: root/sha1_name.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-08-15 13:02:48 -0700
committerJunio C Hamano <gitster@pobox.com>2012-08-15 13:04:20 -0700
commit3f0350ccd5378520d472fd5e5a8a9fb21db50762 (patch)
tree1934fce04bd4009a14ccd202add23431e093c293 /sha1_name.c
parentd0f1ea6003d97e63110fa7d50bb07f546a909b6e (diff)
downloadgit-3f0350ccd5378520d472fd5e5a8a9fb21db50762.tar.gz
git-3f0350ccd5378520d472fd5e5a8a9fb21db50762.tar.xz
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>
Diffstat (limited to 'sha1_name.c')
0 files changed, 0 insertions, 0 deletions