From 6d8dc99478adeefc1a74f3b4db9336decadddc48 Mon Sep 17 00:00:00 2001 From: Justin Tobler Date: Mon, 15 Dec 2025 14:05:12 -0600 Subject: [PATCH] docs: clarify git-rev-list(1) --filter behavior When using the --filter option for git-rev-list(1), objects that are explicitly provided ignore filters and are always printed unless the --filter-provided-objects option is also specified. Clarify this behavior in the documentation. Signed-off-by: Justin Tobler Signed-off-by: Junio C Hamano --- Documentation/rev-list-options.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/rev-list-options.adoc b/Documentation/rev-list-options.adoc index d9665d82c8..453ec59057 100644 --- a/Documentation/rev-list-options.adoc +++ b/Documentation/rev-list-options.adoc @@ -983,7 +983,9 @@ to name units in KiB, MiB, or GiB. For example, `blob:limit=1k` is the same as 'blob:limit=1024'. + The form `--filter=object:type=(tag|commit|tree|blob)` omits all objects -which are not of the requested type. +which are not of the requested type. Note that explicitly provided objects +ignore filters and are always printed unless `--filter-provided-objects` is +also specified. + The form `--filter=sparse:oid=` uses a sparse-checkout specification contained in the blob (or blob-expression) __