git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 7/8] promisor-remote: auto-configure unknown remotes

From
Toon Claes <toon@iotcl.com>
Date
May 11, 2026, 13:06 UTC
Message-ID
<87v7cunlid.fsf@toon--20250203-5JQV3.mail-host-address-is-not-set>
In-Reply-To
<20260427124108.3524129-8-christian.couder@gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 202 quoted lines
> Previous commits have introduced the `promisor.acceptFromServerUrl`
> config variable to allowlist some URLs advertised by a server through
> the "promisor-remote" protocol capability.
>
> However the new `promisor.acceptFromServerUrl` mechanism, like the old
> `promisor.acceptFromServer` mechanism, still requires a remote to
> already exist in the client's local configuration before it can be
> accepted. This places a significant manual burden on users to
> pre-configure these remotes, and creates friction for administrators
> who have to troubleshoot or manually provision these setups for their
> teams.
>
> To eliminate this burden, let's automatically create a new `[remote]`
> section in the client's config when a server advertises an unknown
> remote whose URL matches a `promisor.acceptFromServerUrl` glob pattern.
>
> Concretely, let's add four helpers:
>
>  - sanitize_remote_name(): turn an arbitrary URL-derived string into a
>    valid remote name by replacing non-alphanumeric characters,
>    collapsing runs of '-', and prepending "promisor-auto-".
>
>  - promisor_remote_name_from_url(): normalize the URL and extract
>    host+port+path to build a human-readable base name, then pass it
>    through sanitize_remote_name().
>
>  - configure_auto_promisor_remote(): write the remote.*.url,
>    remote.*.promisor and remote.*.advertisedAs keys to the repo
>    config.
>
>  - handle_matching_allowed_url(): pick the final name (user-supplied
>    alias or auto-generated), handle collisions by appending "-1",
>    "-2", etc., then call configure_auto_promisor_remote().
>
> Let's also add should_accept_new_remote_url() which reuses the
> url_matches_accept_list() helper introduced in a previous commit to
> find a matching pattern, then delegates to handle_matching_allowed_url()
> to create the remote.
>
> And then let's call should_accept_new_remote_url() from the '!item'
> (unknown remote) branch of should_accept_remote(), setting
> `reload_config` so that the newly-written config is picked up.
>
> Finally let's document all that by:
>
>  - expanding the `promisor.acceptFromServerUrl` entry to describe
>    auto-creation, the optional "name=" prefix syntax, the
>    "promisor-auto-*" generation rules, and numeric-suffix collision
>    handling, and by
>  - adding a "remote.<name>.advertisedAs" entry to "remote.adoc".
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
>  Documentation/config/promisor.adoc    |  26 +++-
>  Documentation/config/remote.adoc      |   9 ++
>  promisor-remote.c                     | 202 +++++++++++++++++++++++++-
>  t/t5710-promisor-remote-capability.sh | 104 +++++++++++++
>  4 files changed, 332 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/config/promisor.adoc b/Documentation/config/promisor.adoc
> index efc066c3f2..ae1686a6e0 100644
> --- a/Documentation/config/promisor.adoc
> +++ b/Documentation/config/promisor.adoc
> @@ -54,7 +54,8 @@ promisor.acceptFromServer::
>  promisor.acceptFromServerUrl::
>  	A glob pattern to specify which server-advertised URLs a
>  	client is allowed to act on. When a URL matches, the client
> -	will accept the advertised remote as a promisor remote and may
> +	will accept the advertised remote as a promisor remote, may
> +	automatically create a new remote configuration for it and may
>  	automatically accept field updates (such as authentication
>  	tokens) from the server, even if `promisor.acceptFromServer`
>  	is set to `none` (the default).
> @@ -66,9 +67,10 @@ this option in _ANY_ config file read by Git.
>  Be _VERY_ careful with these patterns: `*` matches any sequence of
>  characters within the 'host' and 'path' parts of a URL (but cannot
>  cross part boundaries). An overly broad pattern is a major security
> -risk, as a matching URL allows a server to update fields (such as
> -authentication tokens) on known remotes without further confirmation.
> -To minimize security risks, follow these guidelines:
> +risk, as a matching URL allows a server to auto-configure new remotes
> +and to update fields (such as authentication tokens) on known remotes
> +without further confirmation. To minimize security risks, follow these
> +guidelines:
>  +
>  1. Start with a secure protocol scheme, like `https://` or `ssh://`.
>  +
> @@ -99,6 +101,22 @@ are resolved. The port must also match exactly (e.g.,
>  `https://example.com:8080/*` will not match a URL advertised on
>  port 9999).
>  +
> +The glob pattern can optionally be prefixed with a remote name and an
> +equals sign (e.g., `cdn=https://cdn.example.com/*`). If such a prefix
> +is provided, accepted remotes will be saved under that name. If no
> +such prefix is provided, a safe remote name will be automatically
> +generated by sanitizing the URL and prefixing it with
> +`promisor-auto-`.
> ++
> +If a remote with the chosen name already exists but points to a
> +different URL, Git will append a numeric suffix (e.g., `-1`, `-2`) to
> +the name to prevent overwriting existing configurations. You should
> +make sure that this doesn't happen often though, as remotes will be
> +rejected if the numeric suffix increases too much. In all cases, the
> +original name advertised by the server is recorded in the
> +`remote.<name>.advertisedAs` configuration variable for tracing and
> +debugging purposes.
> ++
>  For the security implications of accepting a promisor remote, see the
>  documentation of `promisor.acceptFromServer`. For details on the
>  protocol, see linkgit:gitprotocol-v2[5].
> diff --git a/Documentation/config/remote.adoc b/Documentation/config/remote.adoc
> index 91e46f66f5..6e2bbdf457 100644
> --- a/Documentation/config/remote.adoc
> +++ b/Documentation/config/remote.adoc
> @@ -91,6 +91,15 @@ remote.<name>.promisor::
>  	When set to true, this remote will be used to fetch promisor
>  	objects.
>  
> +remote.<name>.advertisedAs::
> +	When a promisor remote is automatically configured using
> +	information advertised by a server through the
> +	`promisor-remote` protocol capability (see
> +	`promisor.acceptFromServerUrl`), the server's originally
> +	advertised name is saved in this variable. This is for
> +	information, tracing and debugging purposes. Users should not
> +	typically modify or create such configuration entries.
> +
>  remote.<name>.partialclonefilter::
>  	The filter that will be applied when fetching from this	promisor remote.
>  	Changing or clearing this value will only affect fetches for new commits.
> diff --git a/promisor-remote.c b/promisor-remote.c
> index 72d5b94bf7..8c8a798fdb 100644
> --- a/promisor-remote.c
> +++ b/promisor-remote.c
> @@ -816,10 +816,197 @@ static struct allowed_url *url_matches_accept_list(
>  	return NULL;
>  }
>  
> -static int should_accept_remote(enum accept_promisor accept,
> +/*
> + * Sanitize the buffer to make it a valid remote name coming from the
> + * server by:
> + *
> + * - replacing any non alphanumeric character with a '-'
> + * - stripping any leading '-',
> + * - condensing multiple '-' into one,
> + * - prepending "promisor-auto-",
> + * - validating the result.
> + */
> +static int sanitize_remote_name(struct strbuf *buf, const char *url)
> +{
> +	char prev = '-';
> +	for (size_t i = 0; i < buf->len; ) {
> +		if (!isalnum(buf->buf[i]))
> +			buf->buf[i] = '-';
> +		if (prev == '-' && buf->buf[i] == '-') {
> +			strbuf_remove(buf, i, 1);
> +		} else {
> +			prev = buf->buf[i];
> +			i++;
> +		}
> +	}
> +
> +	strbuf_strip_suffix(buf, "-");
> +
> +	if (!buf->len) {
> +		warning(_("couldn't generate a valid remote name from "
> +			  "advertised url '%s', ignoring this remote"), url);
> +		return -1;
> +	}
> +
> +	strbuf_insertstr(buf, 0, "promisor-auto-");
> +
> +	if (!valid_remote_name(buf->buf)) {
> +		warning(_("generated remote name '%s' from advertised url '%s' "
> +			  "is invalid, ignoring this remote"), buf->buf, url);
> +		return -1;
> +	}
> +
> +	return 0;
> +}
> +
> +static char *promisor_remote_name_from_url(const char *url)
> +{
> +	struct url_info url_info = { 0 };
> +	char *normalized = url_normalize(url, &url_info);
> +	struct strbuf buf = STRBUF_INIT;
> +
> +	if (!normalized) {
> +		warning(_("couldn't normalize advertised url '%s', "
> +			  "ignoring this remote"), url);
> +		return NULL;
> +	}
> +
> +	if (url_info.host_len) {
> +		strbuf_add(&buf, normalized + url_info.host_off, url_info.host_len);
> +		strbuf_addch(&buf, '-');
> +	}
> +
> +	if (url_info.port_len) {
> +		strbuf_add(&buf, normalized + url_info.port_off, url_info.port_len);
> +		strbuf_addch(&buf, '-');

If the url doesn't have a path, this could lead to the name being `example-com-8443`. But we have a MAX_REMOTES_WITH_SIMILAR_NAMES at 20, would this be an issue for a second remote without configured name?

As far as I can tell from handle_matching_allowed_url(), it's no issue, because the numeric `-%d` suffix is added and we never atoi() the number from existing remotes in the config.

Show 175 quoted lines
> +	}
> +
> +	if (url_info.path_len) {
> +		strbuf_add(&buf, normalized + url_info.path_off, url_info.path_len);
> +		strbuf_trim_trailing_dir_sep(&buf);
> +		strbuf_strip_suffix(&buf, ".git");
> +	}
> +
> +	free(normalized);
> +
> +	if (sanitize_remote_name(&buf, url)) {
> +		strbuf_release(&buf);
> +		return NULL;
> +	}
> +
> +	return strbuf_detach(&buf, NULL);
> +}
> +
> +static void configure_auto_promisor_remote(struct repository *repo,
> +					   const char *name,
> +					   const char *url,
> +					   const char *advertised_as,
> +					   bool reuse)
> +{
> +	char *key;
> +
> +	if (!reuse) {
> +		fprintf(stderr, _("Auto-creating promisor remote '%s' for URL '%s'\n"),
> +			name, url);
> +
> +		key = xstrfmt("remote.%s.url", name);
> +		repo_config_set_gently(repo, key, url);
> +		free(key);
> +	}
> +
> +	/* NB: when reusing, this promotes an existing non-promisor remote */
> +	key = xstrfmt("remote.%s.promisor", name);
> +	repo_config_set_gently(repo, key, "true");
> +	free(key);
> +
> +	if (advertised_as) {
> +		key = xstrfmt("remote.%s.advertisedAs", name);
> +		repo_config_set_gently(repo, key, advertised_as);
> +		free(key);
> +	}
> +}
> +
> +#define MAX_REMOTES_WITH_SIMILAR_NAMES 20
> +
> +/* Return the allocated local name, or NULL on failure */
> +static char *handle_matching_allowed_url(struct repository *repo,
> +					 char *allowed_name,
> +					 const char *remote_url,
> +					 const char *remote_name)
> +{
> +	char *name;
> +	char *basename = allowed_name ?
> +		xstrdup(allowed_name) :
> +		promisor_remote_name_from_url(remote_url);
> +	int i = 0;
> +	bool reuse = false;
> +
> +	if (!basename)
> +		return NULL;
> +
> +	name = xstrdup(basename);
> +
> +	while (i < MAX_REMOTES_WITH_SIMILAR_NAMES) {
> +		char *url_key = xstrfmt("remote.%s.url", name);
> +		const char *existing_url;
> +		int exists = !repo_config_get_string_tmp(repo, url_key, &existing_url);
> +
> +		free(url_key);
> +
> +		if (!exists)
> +			break; /* Free to use */
> +
> +		if (!strcmp(existing_url, remote_url)) {
> +			reuse = true;
> +			break; /* Same URL, so safe to reuse */
> +		}
> +
> +		i++;
> +		free(name);
> +		name = xstrfmt("%s-%d", basename, i);
> +	}
> +
> +	if (i < MAX_REMOTES_WITH_SIMILAR_NAMES) {
> +		configure_auto_promisor_remote(repo, name,
> +					       remote_url, remote_name,
> +					       reuse);
> +	} else {
> +		warning(_("too many remotes accepted with name like '%s-X', "
> +			  "ignoring this remote"), basename);
> +		FREE_AND_NULL(name);
> +	}
> +
> +	free(basename);
> +	return name;
> +}
> +
> +static int should_accept_new_remote_url(struct repository *repo,
> +					struct string_list *accept_urls,
> +					struct promisor_info *advertised)
> +{
> +	struct allowed_url *allowed = url_matches_accept_list(accept_urls,
> +							     advertised->url);
> +	if (allowed) {
> +		char *name = handle_matching_allowed_url(repo,
> +							 allowed->remote_name,
> +							 advertised->url,
> +							 advertised->name);
> +		if (name) {
> +			free((char *)advertised->local_name);
> +			advertised->local_name = name;
> +			return 1;
> +		}
> +	}
> +
> +	return 0;
> +}
> +
> +static int should_accept_remote(struct repository *repo,
> +				enum accept_promisor accept,
>  				struct promisor_info *advertised,
>  				struct string_list *accept_urls,
> -				struct string_list *config_info)
> +				struct string_list *config_info,
> +				bool *reload_config)
>  {
>  	struct promisor_info *p;
>  	struct string_list_item *item;
> @@ -837,9 +1024,13 @@ static int should_accept_remote(enum accept_promisor accept,
>  	/* Get config info for that promisor remote */
>  	item = string_list_lookup(config_info, remote_name);
>  
> -	if (!item)
> +	if (!item) {
>  		/* We don't know about that remote */
> -		return 0;
> +		int res = should_accept_new_remote_url(repo, accept_urls, advertised);
> +		if (res)
> +			*reload_config = true;
> +		return res;
> +	}
>  
>  	p = item->util;
>  
> @@ -1097,7 +1288,8 @@ static void filter_promisor_remote(struct repository *repo,
>  			string_list_sort(&config_info);
>  		}
>  
> -		if (should_accept_remote(accept, advertised, &accept_urls, &config_info)) {
> +		if (should_accept_remote(repo, accept, advertised, &accept_urls,
> +					 &config_info, &reload_config)) {
>  			if (!store_info)
>  				store_info = store_info_new(repo);
>  			if (promisor_store_advertised_fields(advertised, store_info))
> diff --git a/t/t5710-promisor-remote-capability.sh b/t/t5710-promisor-remote-capability.sh
> index 0659b2ac15..549acff23f 100755
> --- a/t/t5710-promisor-remote-capability.sh
> +++ b/t/t5710-promisor-remote-capability.sh
> @@ -458,6 +458,107 @@ test_expect_success "clone with 'None', URL allowlisted, but client has differen
>  	initialize_server 1 "$oid"
>  '
>  
> +test_expect_success "clone with URL allowlisted and no remote already configured" '
> +	git -C server config promisor.advertise true &&
> +	test_when_finished "rm -rf client" &&
> +	test_when_finished "rm -f full_names" &&
> +
> +	GIT_NO_LAZY_FETCH=0 git clone \
> +		-c promisor.acceptfromserver=None \
> +		-c promisor.acceptFromServerUrl="$ENCODED_TRASH_DIRECTORY_URL/*" \
> +		--no-local --filter="blob:limit=5k" server client &&

So promisor.acceptFromServerUrl only works if promisor.acceptFromServer is "none"? I mean which one should precedence? If promisor.acceptFromServer is set to "all", the promisor remote is accepted by the client, but not saved to the config. Is that intentional? Should we document that?

Show 108 quoted lines
> +	# Check that exactly one remote has been auto-created, identified
> +	# by "remote.<name>.advertisedAs" == "lop".
> +	git -C client config get --all --show-names --regexp \
> +		"remote\..*\.advertisedas" >full_names &&
> +	test_line_count = 1 full_names &&
> +	REMOTE_NAME=$(sed "s/^remote\.\(.*\)\.advertisedas .*$/\1/" full_names) &&
> +
> +	# Check ".url" and ".promisor" values
> +	printf "%s\n" "$TRASH_DIRECTORY_URL/lop" "true" >expect &&
> +	git -C client config "remote.$REMOTE_NAME.url" >actual &&
> +	git -C client config "remote.$REMOTE_NAME.promisor" >>actual &&
> +	test_cmp expect actual &&
> +
> +	# Check that the largest object is still missing on the server
> +	check_missing_objects server 1 "$oid"
> +'
> +
> +test_expect_success "clone with named URL allowlisted and no pre-configured remote" '
> +	git -C server config promisor.advertise true &&
> +	test_when_finished "rm -rf client" &&
> +
> +	GIT_NO_LAZY_FETCH=0 git clone \
> +		-c promisor.acceptfromserver=None \
> +		-c promisor.acceptFromServerUrl="cdn=$ENCODED_TRASH_DIRECTORY_URL/*" \
> +		--no-local --filter="blob:limit=5k" server client &&
> +
> +	# Check that a remote has been auto-created with the right "cdn" name and fields.
> +	printf "%s\n" "$TRASH_DIRECTORY_URL/lop" "true" "lop" >expect &&
> +	git -C client config "remote.cdn.url" >actual &&
> +	git -C client config "remote.cdn.promisor" >>actual &&
> +	git -C client config "remote.cdn.advertisedAs" >>actual &&
> +	test_cmp expect actual &&
> +
> +	# Check that the largest object is still missing on the server
> +	check_missing_objects server 1 "$oid"
> +'
> +
> +test_expect_success "clone with URL allowlisted but colliding name" '
> +	git -C server config promisor.advertise true &&
> +	test_when_finished "rm -rf client" &&
> +
> +	GIT_NO_LAZY_FETCH=0 git clone -c remote.cdn.promisor=true \
> +		-c remote.cdn.fetch="+refs/heads/*:refs/remotes/lop/*" \
> +		-c remote.cdn.url="https://example.com/cdn" \
> +		-c promisor.acceptfromserver=None \
> +		-c promisor.acceptFromServerUrl="cdn=$ENCODED_TRASH_DIRECTORY_URL/*" \
> +		--no-local --filter="blob:limit=5k" server client &&
> +
> +	# Check that a remote has been auto-created with the right "cdn-1" name and fields.
> +	printf "%s\n" "$TRASH_DIRECTORY_URL/lop" "true" "lop" >expect &&
> +	git -C client config "remote.cdn-1.url" >actual &&
> +	git -C client config "remote.cdn-1.promisor" >>actual &&
> +	git -C client config "remote.cdn-1.advertisedAs" >>actual &&
> +	test_cmp expect actual &&
> +
> +	# Check that the original "cdn" remote was not overwritten.
> +	printf "%s\n" "https://example.com/cdn" "true" >expect &&
> +	git -C client config "remote.cdn.url" >actual &&
> +	git -C client config "remote.cdn.promisor" >>actual &&
> +	test_cmp expect actual &&
> +
> +	# Check that the largest object is still missing on the server
> +	check_missing_objects server 1 "$oid"
> +'
> +
> +test_expect_success "clone with URL allowlisted and reusable remote" '
> +	git -C server config promisor.advertise true &&
> +	test_when_finished "rm -rf client" &&
> +
> +	GIT_NO_LAZY_FETCH=0 git clone \
> +		-c remote.cdn.fetch="+refs/heads/*:refs/remotes/lop/*" \
> +		-c remote.cdn.url="$TRASH_DIRECTORY_URL/lop" \
> +		-c promisor.acceptfromserver=None \
> +		-c promisor.acceptFromServerUrl="cdn=$ENCODED_TRASH_DIRECTORY_URL/*" \
> +		--no-local --filter="blob:limit=5k" server client &&
> +
> +	# Check that the existing "cdn" remote has been properly updated.
> +	printf "%s\n" "$TRASH_DIRECTORY_URL/lop" "true" "lop" "+refs/heads/*:refs/remotes/lop/*" >expect &&
> +	git -C client config "remote.cdn.url" >actual &&
> +	git -C client config "remote.cdn.promisor" >>actual &&
> +	git -C client config "remote.cdn.advertisedAs" >>actual &&
> +	git -C client config "remote.cdn.fetch" >>actual &&
> +	test_cmp expect actual &&
> +
> +	# Check that no new "cdn-1" remote has been created.
> +	test_must_fail git -C client config "remote.cdn-1.url" &&
> +
> +	# Check that the largest object is still missing on the server
> +	check_missing_objects server 1 "$oid"
> +'
> +
>  test_expect_success "clone with invalid promisor.acceptFromServerUrl" '
>  	git -C server config promisor.advertise true &&
>  	test_when_finished "rm -rf client" &&
> @@ -472,6 +573,9 @@ test_expect_success "clone with invalid promisor.acceptFromServerUrl" '
>  	# Check that a warning was emitted
>  	test_grep "invalid remote name '\''bad name'\''" err &&
>  
> +	# Check that no remote was auto-created
> +	test_must_fail git -C client config get --regexp "remote\..*\.advertisedas" &&
> +
>  	# Check that the largest object is not missing on the server
>  	check_missing_objects server 0 "" &&
>  
> -- 
> 2.54.0.19.gb68b9497aa
>
>
-- 
Cheers,
Toon
Previous: Christian CouderNext: Christian Couder
Message 80 of 111 in “Implement `promisor.storeFields` and `--filter=auto`”
  1. 0/9 Implement `promisor.storeFields` and `--filter=auto`Christian Couder, Dec 23, 2025
  2. 1/9 promisor-remote: refactor initialising field listsChristian Couder, Dec 23, 2025
  3. 2/9 promisor-remote: allow a client to store fieldsChristian Couder, Dec 23, 2025
  4. Patrick SteinhardtJan 7, 2026
  5. Christian CouderFeb 4, 2026
  6. 3/9 clone: make filter_options local to cmd_clone()Christian Couder, Dec 23, 2025
  7. 4/9 fetch: make filter_options local to cmd_fetch()Christian Couder, Dec 23, 2025
  8. Patrick SteinhardtJan 7, 2026
  9. 5/9 doc: fetch: document `--filter=<filter-spec>` optionChristian Couder, Dec 23, 2025
  10. Jean-Noël AVILADec 26, 2025
  11. Christian CouderFeb 4, 2026
  12. 6/9 list-objects-filter-options: support 'auto' mode for --filterChristian Couder, Dec 23, 2025
  13. Patrick SteinhardtJan 7, 2026
  14. Christian CouderFeb 4, 2026
  15. 7/9 list-objects-filter-options: implement auto filter resolutionChristian Couder, Dec 23, 2025
  16. Patrick SteinhardtJan 7, 2026
  17. Christian CouderFeb 4, 2026
  18. Patrick SteinhardtFeb 11, 2026
  19. Christian CouderFeb 12, 2026
  20. 8/9 promisor-remote: keep advertised filter in memoryChristian Couder, Dec 23, 2025
  21. Patrick SteinhardtJan 7, 2026
  22. Christian CouderFeb 4, 2026
  23. Patrick SteinhardtFeb 11, 2026
  24. Junio C HamanoFeb 11, 2026
  25. Christian CouderFeb 12, 2026
  26. 9/9 fetch-pack: wire up and enable auto filter logicChristian Couder, Dec 23, 2025
  27. Patrick SteinhardtJan 7, 2026
  28. Christian CouderFeb 4, 2026
  29. 0/8 Implement `promisor.storeFields` and `--filter=auto`Christian Couder, Feb 4, 2026
  30. 1/8 promisor-remote: refactor initialising field listsChristian Couder, Feb 4, 2026
  31. 2/8 promisor-remote: allow a client to store fieldsChristian Couder, Feb 4, 2026
  32. 3/8 clone: make filter_options local to cmd_clone()Christian Couder, Feb 4, 2026
  33. 4/8 fetch: make filter_options local to cmd_fetch()Christian Couder, Feb 4, 2026
  34. 5/8 doc: fetch: document `--filter=<filter-spec>` optionChristian Couder, Feb 4, 2026
  35. Patrick SteinhardtFeb 11, 2026
  36. Christian CouderFeb 12, 2026
  37. 6/8 list-objects-filter-options: support 'auto' mode for --filterChristian Couder, Feb 4, 2026
  38. 7/8 promisor-remote: keep advertised filters in memoryChristian Couder, Feb 4, 2026
  39. 8/8 fetch-pack: wire up and enable auto filter logicChristian Couder, Feb 4, 2026
  40. Patrick SteinhardtFeb 11, 2026
  41. Christian CouderFeb 12, 2026
  42. 0/9 Implement `promisor.storeFields` and `--filter=auto`Christian Couder, Feb 12, 2026
  43. 1/9 promisor-remote: refactor initialising field listsChristian Couder, Feb 12, 2026
  44. 2/9 promisor-remote: allow a client to store fieldsChristian Couder, Feb 12, 2026
  45. 3/9 clone: make filter_options local to cmd_clone()Christian Couder, Feb 12, 2026
  46. 4/9 fetch: make filter_options local to cmd_fetch()Christian Couder, Feb 12, 2026
  47. 5/9 doc: fetch: document `--filter=<filter-spec>` optionChristian Couder, Feb 12, 2026
  48. 6/9 list-objects-filter-options: support 'auto' mode for --filterChristian Couder, Feb 12, 2026
  49. Jeff KingFeb 14, 2026
  50. Christian CouderFeb 16, 2026
  51. 7/9 promisor-remote: keep advertised filters in memoryChristian Couder, Feb 12, 2026
  52. 8/9 promisor-remote: change promisor_remote_reply()'s signatureChristian Couder, Feb 12, 2026
  53. Patrick SteinhardtFeb 13, 2026
  54. 9/9 fetch-pack: wire up and enable auto filter logicChristian Couder, Feb 12, 2026
  55. Patrick SteinhardtFeb 13, 2026
  56. Patrick SteinhardtFeb 13, 2026
  57. 0/9 Implement `promisor.storeFields` and `--filter=auto`Christian Couder, Feb 16, 2026
  58. 1/9 promisor-remote: refactor initialising field listsChristian Couder, Feb 16, 2026
  59. 2/9 promisor-remote: allow a client to store fieldsChristian Couder, Feb 16, 2026
  60. 3/9 clone: make filter_options local to cmd_clone()Christian Couder, Feb 16, 2026
  61. 4/9 fetch: make filter_options local to cmd_fetch()Christian Couder, Feb 16, 2026
  62. 5/9 doc: fetch: document `--filter=<filter-spec>` optionChristian Couder, Feb 16, 2026
  63. 6/9 list-objects-filter-options: support 'auto' mode for --filterChristian Couder, Feb 16, 2026
  64. 7/9 promisor-remote: keep advertised filters in memoryChristian Couder, Feb 16, 2026
  65. 8/9 promisor-remote: change promisor_remote_reply()'s signatureChristian Couder, Feb 16, 2026
  66. 9/9 fetch-pack: wire up and enable auto filter logicChristian Couder, Feb 16, 2026
  67. 0/8 Auto-configure advertised remotes via URL allowlistChristian Couder, Apr 27, 2026
  68. 1/8 t5710: simplify 'mkdir X' followed by 'git -C X init'Christian Couder, Apr 27, 2026
  69. 2/8 urlmatch: change 'allow_globs' arg to boolChristian Couder, Apr 27, 2026
  70. 3/8 urlmatch: add url_normalize_pattern() helperChristian Couder, Apr 27, 2026
  71. 4/8 promisor-remote: add 'local_name' to 'struct promisor_info'Christian Couder, Apr 27, 2026
  72. Toon ClaesMay 4, 2026
  73. 5/8 promisor-remote: introduce promisor.acceptFromServerUrlChristian Couder, Apr 27, 2026
  74. 6/8 promisor-remote: trust known remotes matching acceptFromServerUrlChristian Couder, Apr 27, 2026
  75. Toon ClaesMay 8, 2026
  76. Christian CouderMay 19, 2026
  77. Toon ClaesMay 11, 2026
  78. Christian CouderMay 19, 2026
  79. 7/8 promisor-remote: auto-configure unknown remotesChristian Couder, Apr 27, 2026
  80. Toon ClaesMay 11, 2026
  81. Christian CouderMay 19, 2026
  82. 8/8 doc: promisor: improve acceptFromServer entryChristian Couder, Apr 27, 2026
  83. Christian CouderApr 27, 2026
  84. 0/8 Auto-configure advertised remotes via URL allowlistChristian Couder, May 19, 2026
  85. 1/8 t5710: simplify 'mkdir X' followed by 'git -C X init'Christian Couder, May 19, 2026
  86. 2/8 urlmatch: change 'allow_globs' arg to boolChristian Couder, May 19, 2026
  87. 3/8 urlmatch: add url_normalize_pattern() helperChristian Couder, May 19, 2026
  88. 4/8 promisor-remote: add 'local_name' to 'struct promisor_info'Christian Couder, May 19, 2026
  89. Junio C HamanoMay 20, 2026
  90. Christian CouderMay 27, 2026
  91. 5/8 promisor-remote: introduce promisor.acceptFromServerUrlChristian Couder, May 19, 2026
  92. 6/8 promisor-remote: trust known remotes matching acceptFromServerUrlChristian Couder, May 19, 2026
  93. Kristoffer HaugsbakkMay 23, 2026
  94. Christian CouderMay 27, 2026
  95. 7/8 promisor-remote: auto-configure unknown remotesChristian Couder, May 19, 2026
  96. 8/8 doc: promisor: improve acceptFromServer entryChristian Couder, May 19, 2026
  97. 0/8 Auto-configure advertised remotes via URL allowlistChristian Couder, May 27, 2026
  98. 1/8 t5710: simplify 'mkdir X' followed by 'git -C X init'Christian Couder, May 27, 2026
  99. 2/8 urlmatch: change 'allow_globs' arg to boolChristian Couder, May 27, 2026
  100. 3/8 urlmatch: add url_normalize_pattern() helperChristian Couder, May 27, 2026
  101. 4/8 promisor-remote: add 'local_name' to 'struct promisor_info'Christian Couder, May 27, 2026
  102. 5/8 promisor-remote: introduce promisor.acceptFromServerUrlChristian Couder, May 27, 2026
  103. 6/8 promisor-remote: trust known remotes matching acceptFromServerUrlChristian Couder, May 27, 2026
  104. 7/8 promisor-remote: auto-configure unknown remotesChristian Couder, May 27, 2026
  105. 8/8 doc: promisor: improve acceptFromServer entryChristian Couder, May 27, 2026
  106. Kristoffer HaugsbakkJul 4, 2026
  107. Toon ClaesJun 9, 2026
  108. Christian CouderJun 9, 2026
  109. Toon ClaesJun 9, 2026
  110. Junio C HamanoJun 10, 2026
  111. Christian CouderJun 11, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.