projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 769e250 3f0350c)
Merge branch 'jc/maint-rev-list-topo-doc'
authorJunio C Hamano <gitster@pobox.com>
Wed, 22 Aug 2012 18:53:20 +0000 (11:53 -0700)
committerJunio C Hamano <gitster@pobox.com>
Wed, 22 Aug 2012 18:53:20 +0000 (11:53 -0700)
commit4def968e1438373152ff91391202da8adafb5f68
treeb5de1e70ebe6258bf5ec0643b335d380909c1dc9tree | snapshot
parent769e2506d91b05898ca48ca152484c0f6d741192commit | diff
parent3f0350ccd5378520d472fd5e5a8a9fb21db50762commit | diff
Merge branch 'jc/maint-rev-list-topo-doc'

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".

* jc/maint-rev-list-topo-doc:
  rev-list docs: clarify --topo-order description
Documentation/rev-list-options.txt diff1 | diff2 | blob | history
Git—the stupid content tracker