projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1c09789) | patch
user-manual: reorder commit, blob, tree discussion
authorJ. Bruce Fields <bfields@citi.umich.edu>
Sat, 1 Sep 2007 03:26:38 +0000 (23:26 -0400)
committerJ. Bruce Fields <bfields@citi.umich.edu>
Sun, 16 Sep 2007 02:17:23 +0000 (22:17 -0400)
commit513d419c5989b8aaeec1cb1ed356519370079dc1
tree9f83e5b6aabfe01045f521669cf3d64ce5b0c25atree | snapshot
parent1c097891e49042cf7ee4628a58836625fb65016dcommit | diff
user-manual: reorder commit, blob, tree discussion

The bottom-up blog, tree, commit order makes sense unless you want to
give explicit examples--it's easier to discover objects to examine if
you go in the other order....,

Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Documentation/user-manual.txt diff | blob | history
Git—the stupid content tracker