From 9f91da752fa28e405e91dfd6bd7372f897bbae8d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ren=C3=A9=20Scharfe?= Date: Sat, 1 Oct 2022 12:26:34 +0200 Subject: [PATCH] revisions.txt: unspecify order of resolved parts of ^! MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: Junio C Hamano --- 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.11.4.GIT