@matheusbsbs / matheus-bagliano / commits / c2c6d9302a
Fork 0

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>

Gerrit Pape committed Mar 29, 2007 at 06:42 UTC c2c6d9302a98ae4c4c76822a1c83551c039271a0
1 file changed +8 -8
Documentation/git-rev-parse.txt
+8 -8
@@ -258,14 +258,14 @@ its all parents.
258
259 Here are a handful examples:
260
261 - D A B D
262 - D F A B C D F
263 - ^A G B D
264 - ^A F B C F
265 - G...I C D F G I
266 - ^B G I C D F G I
267 - F^@ A B C
268 - F^! H D F H
261 + D G H D
262 + D F G H I J D F
263 + ^G D H D
264 + ^D B E I J F B
265 + B...C G H D E B C
266 + ^D B C E I J F B C
267 + C^@ I J F
268 + F^! D G H D F
269
270 Author
271 ------