projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 9dd8175 3f0350c)
Merge branch 'jc/maint-rev-list-topo-doc' into maint-1.7.11
authorJunio C Hamano <gitster@pobox.com>
Fri, 24 Aug 2012 19:05:40 +0000 (12:05 -0700)
committerJunio C Hamano <gitster@pobox.com>
Fri, 24 Aug 2012 19:05:40 +0000 (12:05 -0700)
commit7939a33425d0efabb9d1ce3f94ecbc3ef560c359
tree6af43956135de9c9bea3809313d9afa4f2411314tree | snapshot
parent9dd8175be629c9ed5a102a42df1e6cc3f187eb64commit | diff
parent3f0350ccd5378520d472fd5e5a8a9fb21db50762commit | diff
Merge branch 'jc/maint-rev-list-topo-doc' into maint-1.7.11

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