| commit | c2c6d9302a98ae4c4c76822a1c83551c039271a0 | |
| author | Gerrit Pape <pape@smarden.org> | |
| Thu, 29 Mar 2007 06:42:44 +0000 (29 06:42 +0000) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Thu, 29 Mar 2007 08:38:28 +0000 (29 01:38 -0700) | ||
| tree | dfa55cde4bdfd246d6d089f407edc1fe0534cf02 | treesnapshot (tar.gz zip) |
| parent | 3e63e0df4f1a1610782e679be56ea75f820343fc | commitdiff |
Documentation/git-rev-parse.txt: fix example in SPECIFYING RANGES.
Please see http://bugs.debian.org/404795:
In git-rev-parse(1), there is an example commit tree, which is used twice.
The explanation for this tree is very clear: B and C are commit *parents* to
A.
However, when the tree is reused as an example in the SPECIFYING RANGES, the
manpage author screws up and uses A as a commit *parent* to B and C! I.e.,
he inverts the tree.
And the fact that for this example you need to read the tree backwards is
not explained anywhere (and it would be confusing even if it was).
Signed-off-by: Gerrit Pape <pape@smarden.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Please see http://bugs.debian.org/404795:
In git-rev-parse(1), there is an example commit tree, which is used twice.
The explanation for this tree is very clear: B and C are commit *parents* to
A.
However, when the tree is reused as an example in the SPECIFYING RANGES, the
manpage author screws up and uses A as a commit *parent* to B and C! I.e.,
he inverts the tree.
And the fact that for this example you need to read the tree backwards is
not explained anywhere (and it would be confusing even if it was).
Signed-off-by: Gerrit Pape <pape@smarden.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| Documentation/git-rev-parse.txt | diffblobblamehistory |