aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKai Koponen <kaikoponen@google.com>2024-12-03 12:14:34 -0500
committerJunio C Hamano <gitster@pobox.com>2024-12-04 08:27:58 +0900
commitbc1a980759bc61a426c26d3b47e2d77a708a038b (patch)
treecb1574be1c4c8975aae05a923740d7df73f91875
parentGit 2.40.3 (diff)
downloadgit-bc1a980759bc61a426c26d3b47e2d77a708a038b.tar.gz
git-bc1a980759bc61a426c26d3b47e2d77a708a038b.zip
doc: mention rev-list --ancestry-path restrictions
The rev-list documentation doesn't mention that the given commit must be in the specified commit range, leading to unexpected results. Signed-off-by: Kai Koponen <kaikopone@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/rev-list-options.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 0d90d5b154..9d5243e0aa 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -401,7 +401,8 @@ Default mode::
--ancestry-path[=<commit>]::
When given a range of commits to display (e.g. 'commit1..commit2'
- or 'commit2 {caret}commit1'), only display commits in that range
+ or 'commit2 {caret}commit1'), and a commit <commit> in that range,
+ only display commits in that range
that are ancestors of <commit>, descendants of <commit>, or
<commit> itself. If no commit is specified, use 'commit1' (the
excluded part of the range) as <commit>. Can be passed multiple