projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9a40fcc) | patch
Split cmd now processes commits in topo order.
authorJesse Greenwald <jesse.greenwald@gmail.com>
Tue, 9 Nov 2010 14:34:49 +0000 (08:34 -0600)
committerAvery Pennarun <apenwarr@gmail.com>
Wed, 10 Nov 2010 05:20:32 +0000 (21:20 -0800)
commit6f4f84fa2a03f441826f323c291ca6566acd0d3a
tree1918dbf26f16d7c2a303e64c08e1c4de776604b7tree | snapshot
parent9a40fcc2014cc4a85eca71f81ff4c86d49b7a9e2commit | diff
Split cmd now processes commits in topo order.

Added the "--topo-order" option to git rev-list.  Without this, it seems that
the revision list is coming back in reverse order but it is sorted
chronologically.  This does not gurantee that parent commits are handled
before child commits.
git-subtree.sh diff | blob | history
Git—the stupid content tracker