From: Christian Couder Date: Mon, 16 Feb 2026 13:23:11 GMT Subject: [PATCH v4 5/9] doc: fetch: document `--filter=` option Message-ID: <20260216132317.15894-6-christian.couder@gmail.com> In-Reply-To: <20260216132317.15894-1-christian.couder@gmail.com> The `--filter=` option is documented in most commands that support it except `git fetch`. Let's fix that and document this option. To ensure consistency across commands, let's reuse the exact description currently found in `git clone`. Signed-off-by: Christian Couder --- Documentation/fetch-options.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/fetch-options.adoc b/Documentation/fetch-options.adoc index fcba46ee9e..1ef9807d00 100644 --- a/Documentation/fetch-options.adoc +++ b/Documentation/fetch-options.adoc @@ -88,6 +88,16 @@ linkgit:git-config[1]. This is incompatible with `--recurse-submodules=(yes|on-demand)` and takes precedence over the `fetch.output` config option. +`--filter=`:: + Use the partial clone feature and request that the server sends + a subset of reachable objects according to a given object filter. + When using `--filter`, the supplied __ is used for + the partial fetch. For example, `--filter=blob:none` will filter + out all blobs (file contents) until needed by Git. Also, + `--filter=blob:limit=` will filter out all blobs of size + at least __. For more details on filter specifications, see + the `--filter` option in linkgit:git-rev-list[1]. + ifndef::git-pull[] `--write-fetch-head`:: `--no-write-fetch-head`:: -- 2.53.0.77.g4627d513d6