From: Kai Koponen via GitGitGadget Date: Tue, 03 Dec 2024 20:18:03 GMT Subject: [PATCH] doc: mention rev-list --ancestry-path restrictions Message-ID: From: Kai Koponen The rev-list documention doesn't mention that the given commit must be in the specified commit range, leading to unexpected results. Signed-off-by: Kai Koponen --- doc: mention rev-list --ancestry-path restrictions Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1838%2Fgkaikoponen%2Fmaster-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1838/gkaikoponen/master-v1 Pull-Request: https://github.com/git/git/pull/1838 Documentation/rev-list-options.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt index 00ccf687441..459e5a02f52 100644 --- a/Documentation/rev-list-options.txt +++ b/Documentation/rev-list-options.txt @@ -412,7 +412,8 @@ Default mode:: --ancestry-path[=]:: 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 in that range, + only display commits in that range that are ancestors of , descendants of , or itself. If no commit is specified, use 'commit1' (the excluded part of the range) as . Can be passed multiple base-commit: cc01bad4a9f566cf4453c7edd6b433851b0835e2 -- gitgitgadget