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>
René Scharfe committed
Oct 1, 2022 at 12:26 UTC
9f91da752fa28e405e91dfd6bd7372f897bbae8d
1 file changed
+1
-1
Documentation/revisions.txt
+1
-1
@@ -363,7 +363,7 @@ Revision Range Summary
363
364
'<rev>{caret}!', e.g. 'HEAD{caret}!'::
365
A suffix '{caret}' followed by an exclamation mark is the same
366
- as giving commit '<rev>' and then all its parents prefixed with
366
+ as giving commit '<rev>' and all its parents prefixed with
367
'{caret}' to exclude them (and their ancestors).
368
369
'<rev>{caret}-<n>', e.g. 'HEAD{caret}-, HEAD{caret}-2'::