[PATCH v3 2/3] revisions.txt: unspecify order of resolved parts of ^!
- From
René Scharfe <l.s.r@web.de>
- Date
- Oct 1, 2022, 10:26 UTC
- Message-ID
- <970fd3b1-8792-cc59-c3ee-00656a0615d0@web.de>
- In-Reply-To
- <16c49d20-cafc-4b48-3c6b-e11c74c29abb@web.de>
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> --- 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 '<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':: -- 2.37.3