From: Patrick Steinhardt <ps@pks.im>
To: Alan Braithwaite via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com,
jonathantanmy@google.com, me@ttaylorr.com, gitster@pobox.com,
Jeff King <peff@peff.net>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Alan Braithwaite <alan@braithwaite.dev>
Subject: Re: [PATCH v5] clone: add clone.<url>.defaultObjectFilter config
Date: Wed, 11 Mar 2026 08:44:13 +0100 [thread overview]
Message-ID: <abEdTQrRtAveH1rB@pks.im> (raw)
In-Reply-To: <pull.2058.v5.git.1772847236966.gitgitgadget@gmail.com>
On Sat, Mar 07, 2026 at 01:33:56AM +0000, Alan Braithwaite via GitGitGadget wrote:
> diff --git a/Documentation/config/clone.adoc b/Documentation/config/clone.adoc
> index 0a10efd174..1d6c0957a0 100644
> --- a/Documentation/config/clone.adoc
> +++ b/Documentation/config/clone.adoc
> @@ -21,3 +21,37 @@ endif::[]
> If a partial clone filter is provided (see `--filter` in
> linkgit:git-rev-list[1]) and `--recurse-submodules` is used, also apply
> the filter to submodules.
> +
> +`clone.defaultObjectFilter`::
> +`clone.<url>.defaultObjectFilter`::
> + When set to a filter spec string (e.g., `blob:limit=1m`,
> + `blob:none`, `tree:0`), linkgit:git-clone[1] will automatically
> + use `--filter=<value>` to enable partial clone behavior.
> + Objects matching the filter are excluded from the initial
> + transfer and lazily fetched on demand (e.g., during checkout).
> + Subsequent fetches inherit the filter via the per-remote config
> + that is written during the clone.
> ++
> +The bare `clone.defaultObjectFilter` applies to all clones. The
> +URL-qualified form `clone.<url>.defaultObjectFilter` restricts the
> +setting to clones whose URL matches `<url>`, following the same
> +rules as `http.<url>.*` (see linkgit:git-config[1]). The most
> +specific URL match wins. You can match a domain, a namespace, or a
> +specific project:
> ++
> +----
> +[clone]
> + defaultObjectFilter = blob:limit=1m
> +
> +[clone "https://github.com/"]
> + defaultObjectFilter = blob:limit=5m
> +
> +[clone "https://internal.corp.com/large-project/"]
> + defaultObjectFilter = blob:none
> +----
> ++
> +An explicit `--filter` option on the command line takes precedence
> +over this config, and `--no-filter` defeats it entirely to force a
> +full clone. Only affects the initial clone; it has no effect on
> +later fetches into an existing repository. If the server does not
> +support object filtering, the setting is silently ignored.
This all reads good to me.
> diff --git a/builtin/clone.c b/builtin/clone.c
> index 45d8fa0eed..1207655815 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -757,6 +758,47 @@ static int git_clone_config(const char *k, const char *v,
> return git_default_config(k, v, ctx, cb);
> }
>
> +static int clone_filter_collect(const char *var, const char *value,
> + const struct config_context *ctx UNUSED,
> + void *cb)
> +{
> + char **filter_spec_p = cb;
> +
> + if (!strcmp(var, "clone.defaultobjectfilter")) {
> + if (!value)
> + return config_error_nonbool(var);
> + free(*filter_spec_p);
> + *filter_spec_p = xstrdup(value);
> + }
> + return 0;
> +}
> +
> +/*
> + * Look up clone.defaultObjectFilter or clone.<url>.defaultObjectFilter
> + * using the urlmatch infrastructure. A URL-qualified entry that matches
> + * the clone URL takes precedence over the bare form, following the same
> + * rules as http.<url>.* configuration variables.
> + */
> +static char *get_default_object_filter(const char *url)
> +{
> + struct urlmatch_config config = URLMATCH_CONFIG_INIT;
> + char *filter_spec = NULL;
> + char *normalized_url;
> +
> + config.section = "clone";
> + config.key = "defaultobjectfilter";
> + config.collect_fn = clone_filter_collect;
> + config.cb = &filter_spec;
> +
> + normalized_url = url_normalize(url, &config.url);
`url_normalize()` will return a `NULL` pointer in case it cannot parse
the URL. We need to be prepared for this, otherwise we might segfault.
I guess the best route is to simply ignore the URL in that case --
otherwise, we would always error out in case the remote has a weird URL
configured.
> diff --git a/t/t5616-partial-clone.sh b/t/t5616-partial-clone.sh
> index 1e354e057f..1254901f3e 100755
> --- a/t/t5616-partial-clone.sh
> +++ b/t/t5616-partial-clone.sh
> @@ -722,6 +722,124 @@ test_expect_success 'after fetching descendants of non-promisor commits, gc work
> git -C partial gc --prune=now
> '
>
> +# Test clone.<url>.defaultObjectFilter config
> +
> +test_expect_success 'setup for clone.defaultObjectFilter tests' '
> + git init default-filter-src &&
> + echo "small" >default-filter-src/small.txt &&
> + dd if=/dev/zero of=default-filter-src/large.bin bs=1024 count=100 2>/dev/null &&
> + git -C default-filter-src add . &&
> + git -C default-filter-src commit -m "initial" &&
> +
> + git clone --bare "file://$(pwd)/default-filter-src" default-filter-srv.bare &&
> + git -C default-filter-srv.bare config --local uploadpack.allowfilter 1 &&
> + git -C default-filter-srv.bare config --local uploadpack.allowanysha1inwant 1
> +'
> +
> +test_expect_success 'clone with clone.<url>.defaultObjectFilter applies filter' '
> + SERVER_URL="file://$(pwd)/default-filter-srv.bare" &&
> + git -c "clone.$SERVER_URL.defaultObjectFilter=blob:limit=1k" clone \
> + "$SERVER_URL" default-filter-clone &&
Do we want to "test_when_finished rm -rf default-filter-clone" here and
for all the subsequent tests?
Patrick
next prev parent reply other threads:[~2026-03-11 7:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 16:44 [PATCH] fetch, clone: add fetch.blobSizeLimit config Alan Braithwaite via GitGitGadget
2026-03-02 11:53 ` Patrick Steinhardt
2026-03-02 18:28 ` Jeff King
2026-03-02 18:57 ` Junio C Hamano
2026-03-02 21:36 ` Alan Braithwaite
2026-03-03 6:30 ` Patrick Steinhardt
2026-03-03 14:00 ` Alan Braithwaite
2026-03-03 15:08 ` Patrick Steinhardt
2026-03-03 17:58 ` Junio C Hamano
2026-03-04 5:07 ` Patrick Steinhardt
2026-03-03 17:05 ` Junio C Hamano
2026-03-03 14:34 ` Jeff King
2026-03-05 0:57 ` [PATCH v2] clone: add clone.<url>.defaultObjectFilter config Alan Braithwaite via GitGitGadget
2026-03-05 19:01 ` Junio C Hamano
2026-03-05 23:11 ` Alan Braithwaite
2026-03-06 6:55 ` [PATCH v3] " Alan Braithwaite via GitGitGadget
2026-03-06 10:39 ` brian m. carlson
2026-03-06 19:33 ` Junio C Hamano
2026-03-06 21:50 ` Alan Braithwaite
2026-03-06 21:47 ` [PATCH v4] " Alan Braithwaite via GitGitGadget
2026-03-06 22:18 ` Junio C Hamano
2026-03-07 1:04 ` Alan Braithwaite
2026-03-07 1:33 ` [PATCH v5] " Alan Braithwaite via GitGitGadget
2026-03-11 7:44 ` Patrick Steinhardt [this message]
2026-03-15 1:33 ` Alan Braithwaite
2026-03-15 5:37 ` [PATCH v6] " Alan Braithwaite via GitGitGadget
2026-03-15 21:32 ` Junio C Hamano
2026-03-16 7:47 ` Patrick Steinhardt
2026-05-11 2:38 ` Junio C Hamano
2026-05-11 7:30 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abEdTQrRtAveH1rB@pks.im \
--to=ps@pks.im \
--cc=alan@braithwaite.dev \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.