[PATCH] Documentation/git-rev-parse.txt: fix example in SPECIFYING RANGES.
- From
Gerrit Pape <pape@smarden.org>
- Date
- Mar 29, 2007, 06:42 UTC
- Message-ID
- <20070329064244.32053.qmail@f726f3c4b7218b.315fe32.mid.smarden.org>
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> --- Documentation/git-rev-parse.txt | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt index ccc66aa..a8bf656 100644 --- a/Documentation/git-rev-parse.txt +++ b/Documentation/git-rev-parse.txt @@ -265,14 +265,14 @@ its all parents. Here are a handful examples: - D A B D - D F A B C D F - ^A G B D - ^A F B C F - G...I C D F G I - ^B G I C D F G I - F^@ A B C - F^! H D F H + D G H D + D F G H I J D F + ^G D H D + ^D B E I J F B + B...C G H D E B C + ^D B C E I J F B C + C^@ I J F + F^! D G H D F Author ------
-- 1.5.1-rc2.GIT