From: Jean-Noël AVILA Date: Fri, 26 Dec 2025 13:33:38 GMT Subject: Re: [PATCH 5/9] doc: fetch: document `--filter=` option Message-ID: <4702585.LvFx2qVVIh@cayenne> In-Reply-To: <20251223111113.47473-6-christian.couder@gmail.com> On Tuesday, 23 December 2025 12:11:09 CET Christian Couder wrote: > The `--filter=` option is documented in most commands that > support it except `git fetch`. > > Let's fix that and document that option properly in the same way as it > is already documented for `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..70a9818331 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=:: The option itself must also be back-ticked. `--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 Isn't this second sentence redundant? What new information is brought? > + 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`:: Thank you Jean-Noël