From: René Scharfe <l.s.r@web.de>
Date: Sat, 1 Oct 2022 10:26:34 +0000 (+0200)
Subject: revisions.txt: unspecify order of resolved parts of ^!
X-Git-Tag: v2.39.0-rc0~87^2~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9f91da752fa28e405e91dfd6bd7372f897bbae8d;p=thirdparty%2Fgit.git

revisions.txt: unspecify order of resolved parts of ^!

gitrevisions(7) says that <rev>^! resolves to <rev> and then all the
parents of <rev>.  revision.c::handle_revision_arg_1() actually adds
all parents first, then <rev>.  Change the documentation to leave the
order unspecified, to avoid misleading readers.

Signed-off-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---

diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index e3e350126d..0d2e55d781 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/revisions.txt
@@ -363,7 +363,7 @@ Revision Range Summary
 
 '<rev>{caret}!', e.g. 'HEAD{caret}!'::
   A suffix '{caret}' followed by an exclamation mark is the same
-  as giving commit '<rev>' and then all its parents prefixed with
+  as giving commit '<rev>' and all its parents prefixed with
   '{caret}' to exclude them (and their ancestors).
 
 '<rev>{caret}-<n>', e.g. 'HEAD{caret}-, HEAD{caret}-2'::