From: René Scharfe Date: Sat, 01 Oct 2022 10:26:34 GMT Subject: [PATCH v3 2/3] revisions.txt: unspecify order of resolved parts of ^! Message-ID: <970fd3b1-8792-cc59-c3ee-00656a0615d0@web.de> In-Reply-To: <16c49d20-cafc-4b48-3c6b-e11c74c29abb@web.de> gitrevisions(7) says that ^! resolves to and then all the parents of . revision.c::handle_revision_arg_1() actually adds all parents first, then . Change the documentation to leave the order unspecified, to avoid misleading readers. Signed-off-by: René Scharfe --- Documentation/revisions.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 '{caret}!', e.g. 'HEAD{caret}!':: A suffix '{caret}' followed by an exclamation mark is the same - as giving commit '' and then all its parents prefixed with + as giving commit '' and all its parents prefixed with '{caret}' to exclude them (and their ancestors). '{caret}-', e.g. 'HEAD{caret}-, HEAD{caret}-2':: -- 2.37.3