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

[PATCH v12 0/5] fetch: avoid fetching every branch of a new remote in a shallow repo

From
Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 27, 2026, 12:24 UTC
Message-ID
<pull.2412.v12.git.git.1793103884.gitgitgadget@gmail.com>
In-Reply-To
<pull.2412.git.git.1789829246437.gitgitgadget@gmail.com>
Avoid fetching every branch of a new remote in a shallow repo.
Changes in v12:
 * Renamed remote.<name>.refmap to remote.<name>.fetchRefmap throughout
   code, docs, and tests, so it reads unambiguously as fetch-only.
 * Added the missing code path in get_ref_map() so a branch fetched by name
   via remote.<name>.fetch is also stored through remote.<name>.fetchRefmap,
   with a new test (the "cabal" example: fetch = master/next/seen plus a
   refmap storing them all under one namespace).
 * Reworded the fetchRefmap commit message and doc entry to drop a redundant
   sentence, fix a confusing paragraph, and spell out that
   remote.<name>.fetch, when configured, still decides what's fetched while
   the refmap only remaps it.
 * Added a prefetch coverage test to t5586-fetch-refmap.sh.
Changes in v11:
 * remote_find_tracking() now falls back to remote.<name>.refmap when
   remote.<name>.fetch doesn't match. Negative refspecs in fetch still
   exclude refs, and both cases have tests
 * The helpers write straight into a strvec, take the output parameter last
   and the remote as const
 * The followRemoteHEAD lookup is done once, not duplicated in two branches
 * Clearer commit messages and docs: a working example plus a reference to
   49ca2fba39, the goal stated first, an incorrect "used to die" claim
   dropped, and an explanation of why a refmap turns on the inference
 * use_limited_fetch is a bool
Changes in v10:
 * Resolve merge conflict after master integrated
   ch/fetch-followremotehead-lazy-validation.
Changes in v9:
 * Moved the do_fetch() if/else-if/else split out of the preliminary
   helper-extraction commit and into the refmap-inference commit that needs
   it. Preliminary commit is now a simpler refactor.
Changes in v8:
 * Split into a preliminary collect_upstream_from_remote() helper commit
   plus a simplified refmap-inference commit.
 * Fixed a regression that could drop the current branch's @{upstream} when
   remote.<name>.fetch was narrowed.
 * Threaded struct repository * through instead of hardcoding
   the_repository.
 * Minor naming and comment cleanups.
Changes in v7:
 * Fixed fatal: --refmap option is only meaningful with command-line
   refspec(s) firing just from configuring remote.<name>.refmap alone, with
   nothing else to fetch.
 * When both remote.<name>.fetch and remote.<name>.refmap are configured, a
   refspec-less fetch follows .fetch as usual, .refmap only remaps something
   already being fetched by name. Added tests.
Changes in v6:
 * Remove leftover reference to deleted default-branch logic in commit
   message.
Changes in v5:
 * Renumber test file from t5585 to t5586.
Changes in v4:
 * Removed the automatic default-branch fetch. A fresh remote fetches
   nothing until you track a branch explicitly.
 * Fixed fetch report showing "new ref HEAD" instead of "new branch "
 * Reworded remote..refmap docs and commit message.
Changes in v3:
 * Replace the special ":"/"+:" fetch refspec with remote.<name>.refmap,
   reusing git's existing --refmap mechanism instead of inventing new
   refspec syntax.
 * Split the change into 4 commits.
Changes in v2:
 * Replaced the opt-in fetch.shallow config entirely with a new special
   fetch refspec (+:) that git remote add now defaults new remotes to in a
   shallow repository. The new refspec fetches whichever branches any local
   branch tracks at that remote, plus the remote's default branch.
Harald Nordgren (5):
  fetch: add remote.<name>.fetchRefmap
  fetch: extract collect_upstream_from_remote() helper
  fetch: infer branches to fetch from a refmap-only remote
  remote: add "git remote add --limited-fetch"
  remote: default to --limited-fetch in a shallow repository
 Documentation/config/remote.adoc |   9 +++
 Documentation/fetch-options.adoc |  10 +++
 Documentation/git-remote.adoc    |  14 +++-
 builtin/fetch.c                  | 100 +++++++++++++++++------
 builtin/remote.c                 |  31 +++++--
 remote.c                         |  60 +++++++++++++-
 remote.h                         |  20 +++++
 t/meson.build                    |   1 +
 t/t5505-remote.sh                |  76 ++++++++++++++++++
 t/t5510-fetch.sh                 | 130 ++++++++++++++++++++++++++++++
 t/t5586-fetch-refmap.sh          | 133 +++++++++++++++++++++++++++++++
 11 files changed, 551 insertions(+), 33 deletions(-)
 create mode 100755 t/t5586-fetch-refmap.sh
base-commit: 37b3475fb530c14109211faca33716a173db61ed
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2412%2FHaraldNordgren%2Ffetch-shallow-narrow-refspec-v12
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2412/HaraldNordgren/fetch-shallow-narrow-refspec-v12
Pull-Request: https://github.com/git/git/pull/2412
Range-diff vs v11:
 1:  d66b3c0bb1 ! 1:  a1f5e81fdc fetch: add remote.<name>.refmap
     @@ Metadata
      Author: Harald Nordgren <haraldnordgren@gmail.com>
      
       ## Commit message ##
     -    fetch: add remote.<name>.refmap
     +    fetch: add remote.<name>.fetchRefmap
      
     -    Add a per-remote config variable, remote.<name>.refmap, that provides
     -    the default value for --refmap the same way remote.<name>.fetch
     -    already provides the default refspecs to fetch. Like --refmap itself,
     -    it only maps refs that are actually being fetched, so it has nothing
     -    to do when there is nothing explicit to fetch, on the command line or
     -    via remote.<name>.fetch.
     +    Add a per-remote config variable, remote.<name>.fetchRefmap, that
     +    provides the default value for --refmap the same way
     +    remote.<name>.fetch already provides the default refspecs to fetch.
      
     -    A refspec-less fetch with a refmap configured but nothing else to say
     -    what to fetch falls back to the same defaults as a remote with no
     -    refspec or refmap at all. Only an explicit --refmap given on the
     -    command line with no command-line refspec to go with it is still
     -    rejected, since that combination is a plain mistake to type, unlike a
     -    remote.<name>.refmap configured on its own. A remote.<name>.fetch
     -    that is also configured is used as before.
     +    Unlike passing --refmap on the command line, which requires an
     +    explicit refspec to go with it, configuring remote.<name>.fetchRefmap
     +    on its own does not change what a refspec-less fetch does: it falls
     +    back to the same defaults as a remote with no fetchRefmap at all.
     +
     +    When remote.<name>.fetch is also configured, it still decides what to
     +    fetch, and the refmap maps what it fetches. This lets a remote name
     +    only a few branches and store them all through one refmap:
     +
     +        [remote "cabal"]
     +            fetch = master
     +            fetch = next
     +            fetch = seen
     +            fetchRefmap = +refs/heads/*:refs/remotes/cabal/*
     +
     +    Looking up the remote-tracking branch for a remote branch, as
     +    @{upstream} and "git branch --track" do, falls back to the refmap when
     +    remote.<name>.fetch has no match, so that these work for such
     +    branches too. A branch excluded by a negative refspec in
     +    remote.<name>.fetch stays excluded.
      
          Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
      
     @@ Documentation/config/remote.adoc: remote.<name>.fetch::
       	The default set of "refspec" for linkgit:git-fetch[1]. See
       	linkgit:git-fetch[1].
       
     -+remote.<name>.refmap::
     -+	The default value of the `--refmap` option for linkgit:git-fetch[1].
     -+	Used to map remote refs being fetched to remote-tracking refs to
     -+	store. See the `--refmap` entry in linkgit:git-fetch[1].
     ++remote.<name>.fetchRefmap::
     ++	The default value of the `--refmap` option, used to map refs being
     ++	fetched to remote-tracking refs to store, the same way
     ++	`remote.<name>.fetch` does for an explicit refspec.
     ++	`remote.<name>.fetch`, if also configured, still decides what is
     ++	fetched. See the `--refmap` entry in linkgit:git-fetch[1].
      +
       remote.<name>.push::
       	The default set of "refspec" for linkgit:git-push[1]. See
     @@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
       	struct ref **tail = &ref_map;
      +	/*
      +	 * The --refmap command line option, if given, takes precedence
     -+	 * over remote.<name>.refmap.
     ++	 * over remote.<name>.fetchRefmap.
      +	 */
      +	struct refspec *effective_refmap =
      +		refmap.nr ? &refmap : remote ? &remote->refmap : NULL;
       
       	/* opportunistically-updated references: */
       	struct ref *orefs = NULL, **oref_tail = &orefs;
     +@@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
     + 	filter_prefetch_refspec(rs);
     + 	if (remote)
     + 		filter_prefetch_refspec(&remote->fetch);
     ++	if (effective_refmap)
     ++		filter_prefetch_refspec(effective_refmap);
     + 
     + 	if (rs->nr) {
     + 		struct refspec *fetch_refspec;
      @@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
       		 * by ref_remove_duplicates() in favor of one of these
       		 * opportunistic entries with FETCH_HEAD_IGNORE.
     @@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
       		else
       			fetch_refspec = &remote->fetch;
       
     +@@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
     + 			if (has_merge &&
     + 			    !strcmp(branch->remote_name, remote->name))
     + 				add_merge_config(&ref_map, remote_refs, branch, &tail);
     ++
     ++			for (i = 0; i < remote->refmap.nr; i++)
     ++				get_fetch_map(ref_map, &remote->refmap.items[i],
     ++					      &oref_tail, 1);
     + 		} else if (!prefetch) {
     + 			ref_map = get_remote_ref(remote_refs, "HEAD");
     + 			if (!ref_map)
      
       ## remote.c ##
      @@ remote.c: static struct remote *make_remote(struct remote_state *remote_state,
     @@ remote.c: static int handle_config(const char *key, const char *value,
       			return -1;
       		refspec_append(&remote->fetch, v);
       		free(v);
     -+	} else if (!strcmp(subkey, "refmap")) {
     ++	} else if (!strcmp(subkey, "fetchrefmap")) {
      +		char *v;
      +		if (git_config_string(&v, key, value))
      +			return -1;
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
       	)
       '
       
     -+test_expect_success 'remote.*.refmap acts like --refmap on the command line' '
     -+	test_when_finished "git -C three config --unset remote.origin.refmap" &&
     ++test_expect_success 'remote.*.fetchRefmap acts like --refmap on the command line' '
     ++	test_when_finished "git -C three config --unset remote.origin.fetchRefmap" &&
      +	git branch -f side &&
     -+	git -C three config remote.origin.refmap \
     ++	git -C three config remote.origin.fetchRefmap \
      +		"refs/heads/*:refs/remotes/other/*" &&
      +	(
      +		cd three &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +	test_cmp expect actual
      +}
      +
     -+test_expect_success 'remote.<name>.refmap without tracking (baseline)' '
     ++test_expect_success 'remote.<name>.fetchRefmap without tracking (baseline)' '
      +	test_when_finished "rm -fr fetch-refmap-baseline fetch-refmap-upstream" &&
      +	git init -b main fetch-refmap-upstream &&
      +	test_commit -C fetch-refmap-upstream base &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +
      +		# Without fetch refspec, but with fetch refmap.
      +		git config --unset-all remote.origin.fetch &&
     -+		git config remote.origin.refmap "+refs/heads/*:refs/remotes/origin/*" &&
     ++		git config remote.origin.fetchRefmap "+refs/heads/*:refs/remotes/origin/*" &&
      +
      +		# Nothing tracked, nothing fetched, no error.
      +		git fetch origin &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +
      +		# With both refmap and fetch configured, remote.<name>.fetch
      +		# wins: a refspec-less fetch follows it as usual, and
     -+		# remote.<name>.refmap plays no part in deciding what to
     -+		# fetch, only in remapping something that is already being
     -+		# fetched by name.
     ++		# remote.<name>.fetchRefmap plays no part in deciding what to
     ++		# fetch, only in mapping what is fetched.
      +		git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*" &&
      +		git fetch origin &&
      +		check_fetched_refs <<-\EOF
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +	)
      +'
      +
     -+test_expect_success 'remote.<name>.refmap tracks a branch outside remote.<name>.fetch' '
     ++test_expect_success 'remote.<name>.fetchRefmap stores branches named in remote.<name>.fetch' '
     ++	test_when_finished "rm -fr fetch-refmap-upstream downstream" &&
     ++	git init -b master fetch-refmap-upstream &&
     ++	test_commit -C fetch-refmap-upstream base &&
     ++	git -C fetch-refmap-upstream branch next &&
     ++	git -C fetch-refmap-upstream branch seen &&
     ++	git -C fetch-refmap-upstream branch other &&
     ++	git init downstream &&
     ++	(
     ++		cd downstream &&
     ++		git remote add cabal ../fetch-refmap-upstream &&
     ++		git config --unset-all remote.cabal.fetch &&
     ++		git config --add remote.cabal.fetch master &&
     ++		git config --add remote.cabal.fetch next &&
     ++		git config --add remote.cabal.fetch seen &&
     ++		git config remote.cabal.fetchRefmap "+refs/heads/*:refs/remotes/cabal/*" &&
     ++		git fetch cabal &&
     ++		check_fetched_refs <<-\EOF &&
     ++		refs/remotes/cabal/HEAD
     ++		refs/remotes/cabal/master
     ++		refs/remotes/cabal/next
     ++		refs/remotes/cabal/seen
     ++		EOF
     ++		git branch --track topic cabal/next &&
     ++		echo refs/remotes/cabal/next >expect &&
     ++		git rev-parse --symbolic-full-name topic@{upstream} >actual &&
     ++		test_cmp expect actual
     ++	)
     ++'
     ++
     ++test_expect_success 'remote.<name>.fetchRefmap tracks a branch outside remote.<name>.fetch' '
      +	test_when_finished "rm -fr fetch-refmap-upstream downstream" &&
      +	git init -b main fetch-refmap-upstream &&
      +	test_commit -C fetch-refmap-upstream base &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +	(
      +		cd downstream &&
      +		git remote add -t main origin ../fetch-refmap-upstream &&
     -+		git config remote.origin.refmap "+refs/heads/*:refs/remotes/origin/*" &&
     ++		git config remote.origin.fetchRefmap "+refs/heads/*:refs/remotes/origin/*" &&
      +		git fetch origin other &&
      +		git branch --track topic origin/other &&
      +		test_cmp_config origin branch.topic.remote &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +	)
      +'
      +
     -+test_expect_success 'remote.<name>.refmap does not track a branch excluded by remote.<name>.fetch' '
     ++test_expect_success 'remote.<name>.fetchRefmap does not track a branch excluded by remote.<name>.fetch' '
      +	test_when_finished "rm -fr fetch-refmap-upstream downstream" &&
      +	git init -b main fetch-refmap-upstream &&
      +	test_commit -C fetch-refmap-upstream base &&
     @@ t/t5510-fetch.sh: test_expect_success 'explicit --refmap option overrides remote
      +		cd downstream &&
      +		git remote add origin ../fetch-refmap-upstream &&
      +		git config --add remote.origin.fetch "^refs/heads/secret" &&
     -+		git config remote.origin.refmap "+refs/heads/*:refs/remotes/origin/*" &&
     ++		git config remote.origin.fetchRefmap "+refs/heads/*:refs/remotes/origin/*" &&
      +		git fetch origin secret &&
      +		git rev-parse --verify refs/remotes/origin/secret &&
      +		test_must_fail git branch --track topic origin/secret 2>err &&
 2:  f685051033 = 2:  e8af5bc76b fetch: extract collect_upstream_from_remote() helper
 3:  5c76b3b88d ! 3:  aad6e5f66f fetch: infer branches to fetch from a refmap-only remote
     @@ Metadata
       ## Commit message ##
          fetch: infer branches to fetch from a refmap-only remote
      
     -    We want remote.<name>.refmap to work on its own, without also setting
     -    remote.<name>.fetch, so a remote can be limited to the branches
     -    already in use locally, without listing them by hand or touching the
     -    command line every time.
     +    We want remote.<name>.fetchRefmap to work on its own, without also
     +    setting remote.<name>.fetch, so a remote can be limited to the
     +    branches already in use locally, without listing them by hand or
     +    touching the command line every time.
      
          Infer what to fetch from the local branches whose @{upstream} is
          already on that remote. The refmap itself still only controls where
     @@ Commit message
          Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
      
       ## Documentation/config/remote.adoc ##
     -@@ Documentation/config/remote.adoc: remote.<name>.fetch::
     - remote.<name>.refmap::
     - 	The default value of the `--refmap` option for linkgit:git-fetch[1].
     - 	Used to map remote refs being fetched to remote-tracking refs to
     --	store. See the `--refmap` entry in linkgit:git-fetch[1].
     -+	store. If `remote.<name>.fetch` is not set either, a refspec-less
     -+	fetch infers what to fetch from local branches built on this
     -+	remote, instead of needing `remote.<name>.fetch` listed by hand.
     +@@ Documentation/config/remote.adoc: remote.<name>.fetchRefmap::
     + 	fetched to remote-tracking refs to store, the same way
     + 	`remote.<name>.fetch` does for an explicit refspec.
     + 	`remote.<name>.fetch`, if also configured, still decides what is
     +-	fetched. See the `--refmap` entry in linkgit:git-fetch[1].
     ++	fetched. If it is not set either, a refspec-less fetch instead
     ++	infers what to fetch from local branches built on this remote.
      +	See the `--refmap` entry in linkgit:git-fetch[1].
       
       remote.<name>.push::
     @@ Documentation/fetch-options.adoc: endif::git-pull[]
       +
      -`remote.<name>.refmap` provides the default value for this option, the
      -same way `remote.<name>.fetch` provides the default refspecs to fetch.
     -+When a refmap is active (from `--refmap` or `remote.<name>.refmap`) but
     ++When a refmap is active (from `--refmap` or `remote.<name>.fetchRefmap`) but
      +nothing to fetch is specified on the command line, nor is there a
      +`remote.<name>.fetch`, infer what to fetch from local branches built on
      +this remote: remote-tracking branches from this remote that are also
     @@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
       	filter_prefetch_refspec(rs);
       	if (remote)
       		filter_prefetch_refspec(&remote->fetch);
     + 	if (effective_refmap)
     + 		filter_prefetch_refspec(effective_refmap);
       
      +	if (!rs->nr && remote && !remote->fetch.nr &&
      +	    effective_refmap && effective_refmap->nr) {
     @@ builtin/fetch.c: static int do_fetch(struct transport *transport,
      +	} else {
      +		/*
      +		 * The --refmap command line option, if given, takes
     -+		 * precedence over remote.<name>.refmap.
     ++		 * precedence over remote.<name>.fetchRefmap.
      +		 */
      +		struct refspec *effective_refmap = refmap.nr ? &refmap :
      +			&transport->remote->refmap;
     @@ t/t5586-fetch-refmap.sh (new)
      @@
      +#!/bin/sh
      +
     -+test_description='"git fetch" with a remote.<name>.refmap but no remote.<name>.fetch
     ++test_description='"git fetch" with a remote.<name>.fetchRefmap but no remote.<name>.fetch
      +
      +When a remote has a refmap configured but no fetch refspec, a
      +refspec-less fetch infers what to fetch from the local branches whose
     @@ t/t5586-fetch-refmap.sh (new)
      +		cd client &&
      +		git remote add upstream .. &&
      +		test_might_fail git config unset remote.upstream.fetch &&
     -+		git config remote.upstream.refmap \
     ++		git config remote.upstream.fetchRefmap \
      +			"+refs/heads/*:refs/remotes/upstream/*"
      +	)
      +'
     @@ t/t5586-fetch-refmap.sh (new)
      +	)
      +'
      +
     ++test_expect_success 'prefetch stores tracked branches under refs/prefetch/' '
     ++	test_commit main-3 &&
     ++	(
     ++		cd client &&
     ++		git rev-parse refs/remotes/upstream/main >expect &&
     ++		git fetch --prefetch upstream &&
     ++		git rev-parse refs/remotes/upstream/main >actual &&
     ++		test_cmp expect actual &&
     ++		git -C .. rev-parse main >expect &&
     ++		git rev-parse refs/prefetch/remotes/upstream/main >actual &&
     ++		test_cmp expect actual
     ++	)
     ++'
     ++
      +test_expect_success 'git remote show does not choke on a refmap-only remote' '
      +	(
      +		cd client &&
 4:  417f14d708 ! 4:  97650da870 remote: add "git remote add --limited-fetch"
     @@ Commit message
          branches nobody asked for.
      
          Give "git remote add" a --limited-fetch option that sets up
     -    remote.<name>.refmap instead of remote.<name>.fetch, so that
     +    remote.<name>.fetchRefmap instead of remote.<name>.fetch, so that
          "git fetch <name>" only fetches the branches already tracked, as
          described in the previous commit. It is rejected together with
          -t/--track or --mirror, since those already say explicitly what to
     @@ Documentation/git-remote.adoc: the `refs/remotes/<name>/` namespace, a refspec t
       multiple branches without grabbing all branches.
       +
      +With `--limited-fetch` option, instead of a `remote.<name>.fetch` refspec
     -+that tracks all branches, `remote.<name>.refmap` is set up so that a
     ++that tracks all branches, `remote.<name>.fetchRefmap` is set up so that a
      +refspec-less `git fetch <name>` only fetches branches our local branches
      +are built on. See the `--refmap` entry in linkgit:git-fetch[1] for
      +details.
     @@ builtin/remote.c: static int add(int argc, const char **argv, const char *prefix
      -			add_branch(buf.buf, track.items[i].string,
      -				   name, mirror, &buf2);
      +		if (use_limited_fetch) {
     -+			strbuf_addf(&buf, "remote.%s.refmap", name);
     ++			strbuf_addf(&buf, "remote.%s.fetchRefmap", name);
      +			strbuf_reset(&buf2);
      +			strbuf_addf(&buf2, "+refs/heads/*:refs/remotes/%s/*", name);
      +			repo_config_set(the_repository, buf.buf, buf2.buf);
     @@ t/t5505-remote.sh: test_expect_success 'filters are listed by git remote -v only
      +		cd full-add &&
      +		git remote add --limited-fetch upstream ../two &&
      +		test_cmp_config "+refs/heads/*:refs/remotes/upstream/*" \
     -+			remote.upstream.refmap &&
     ++			remote.upstream.fetchRefmap &&
      +		test_must_fail git config get remote.upstream.fetch
      +	)
      +'
 5:  de0daa8623 ! 5:  a802c9f82f remote: default to --limited-fetch in a shallow repository
     @@ Documentation/git-remote.adoc: Add a remote named _<name>_ for the repository at
       the remote information is set up.
       +
      @@ Documentation/git-remote.adoc: With `--limited-fetch` option, instead of a `remote.<name>.fetch` refspec
     - that tracks all branches, `remote.<name>.refmap` is set up so that a
     + that tracks all branches, `remote.<name>.fetchRefmap` is set up so that a
       refspec-less `git fetch <name>` only fetches branches our local branches
       are built on. See the `--refmap` entry in linkgit:git-fetch[1] for
      -details.
     @@ t/t5505-remote.sh: test_expect_success 'filters are listed by git remote -v only
      +		cd shallow-add &&
      +		git remote add upstream ../two &&
      +		test_cmp_config "+refs/heads/*:refs/remotes/upstream/*" \
     -+			remote.upstream.refmap &&
     ++			remote.upstream.fetchRefmap &&
      +		test_must_fail git config get remote.upstream.fetch &&
      +		git fetch upstream main &&
      +		git branch --set-upstream-to=upstream/main &&
     @@ t/t5505-remote.sh: test_expect_success 'filters are listed by git remote -v only
      +		git remote add --no-limited-fetch upstream ../two &&
      +		test_cmp_config "+refs/heads/*:refs/remotes/upstream/*" \
      +			remote.upstream.fetch &&
     -+		test_must_fail git config get remote.upstream.refmap
     ++		test_must_fail git config get remote.upstream.fetchRefmap
      +	)
      +'
      +
-- 
gitgitgadget
Previous: Harald Nordgren via GitGitGadgetNext: Harald Nordgren via GitGitGadget
Message 119 of 152 in “fetch: add config to avoid fetching every branch in shallow repo”
  1. fetch: add config to avoid fetching every branch in shallow repoHarald Nordgren via GitGitGadget, Sep 19, 2026
  2. Phillip WoodSep 21, 2026
  3. Harald NordgrenSep 21, 2026
  4. Harald NordgrenSep 22, 2026
  5. Phillip WoodSep 22, 2026
  6. Harald NordgrenSep 22, 2026
  7. Phillip WoodSep 23, 2026
  8. Junio C HamanoSep 22, 2026
  9. Harald NordgrenSep 22, 2026
  10. Phillip WoodSep 23, 2026
  11. Junio C HamanoSep 23, 2026
  12. D. Ben KnobleSep 23, 2026
  13. Junio C HamanoSep 23, 2026
  14. D. Ben KnobleSep 24, 2026
  15. Junio C HamanoSep 24, 2026
  16. fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Sep 23, 2026
  17. Junio C HamanoSep 23, 2026
  18. 0/4 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Sep 25, 2026
  19. 1/4 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Sep 25, 2026
  20. Junio C HamanoSep 25, 2026
  21. 2/4 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Sep 25, 2026
  22. Junio C HamanoSep 25, 2026
  23. 3/4 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Sep 25, 2026
  24. 4/4 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Sep 25, 2026
  25. 0/4 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Sep 29, 2026
  26. 1/4 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Sep 29, 2026
  27. 2/4 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Sep 29, 2026
  28. Harald NordgrenSep 29, 2026
  29. Junio C HamanoSep 29, 2026
  30. 3/4 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Sep 29, 2026
  31. 4/4 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Sep 29, 2026
  32. Junio C HamanoSep 29, 2026
  33. 0/4 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 2, 2026
  34. 1/4 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 2, 2026
  35. 2/4 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 2, 2026
  36. 3/4 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 2, 2026
  37. Junio C HamanoOct 2, 2026
  38. 4/4 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 2, 2026
  39. 0/4 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 4, 2026
  40. 1/4 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 4, 2026
  41. 2/4 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 4, 2026
  42. 3/4 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 4, 2026
  43. 4/4 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 4, 2026
  44. Junio C HamanoOct 4, 2026
  45. Harald NordgrenOct 4, 2026
  46. Junio C HamanoOct 5, 2026
  47. Harald NordgrenOct 5, 2026
  48. 0/4 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 7, 2026
  49. 1/4 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 7, 2026
  50. 2/4 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 7, 2026
  51. Junio C HamanoOct 8, 2026
  52. Harald NordgrenOct 9, 2026
  53. Harald NordgrenOct 9, 2026
  54. 3/4 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 7, 2026
  55. 4/4 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 7, 2026
  56. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 10, 2026
  57. 1/5 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 10, 2026
  58. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 10, 2026
  59. Junio C HamanoOct 10, 2026
  60. Harald NordgrenOct 10, 2026
  61. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 10, 2026
  62. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 10, 2026
  63. Junio C HamanoOct 10, 2026
  64. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 10, 2026
  65. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 14, 2026
  66. 1/5 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 14, 2026
  67. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 14, 2026
  68. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 14, 2026
  69. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 14, 2026
  70. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 14, 2026
  71. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 20, 2026
  72. 1/5 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 20, 2026
  73. D. Ben KnobleOct 24, 2026
  74. Harald NordgrenOct 24, 2026
  75. D. Ben KnobleOct 25, 2026
  76. Harald NordgrenOct 25, 2026
  77. Junio C HamanoOct 25, 2026
  78. Harald NordgrenOct 26, 2026
  79. Junio C HamanoOct 26, 2026
  80. Phillip WoodOct 27, 2026
  81. Junio C HamanoOct 27, 2026
  82. Phillip WoodOct 28, 2026
  83. Junio C HamanoOct 28, 2026
  84. Harald NordgrenOct 28, 2026
  85. Phillip WoodOct 29, 2026
  86. Junio C HamanoOct 29, 2026
  87. Phillip WoodOct 26, 2026
  88. Junio C HamanoOct 26, 2026
  89. Phillip WoodOct 26, 2026
  90. Ben KnobleOct 29, 2026
  91. Harald NordgrenOct 29, 2026
  92. Junio C HamanoOct 29, 2026
  93. Harald NordgrenOct 30, 2026
  94. Notes, refs, etc. (was: Re: [PATCH v10 1/5] fetch: add remote.<name>.refmap)D. Ben Knoble, Nov 7, 2026
  95. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 20, 2026
  96. D. Ben KnobleOct 24, 2026
  97. Harald NordgrenOct 25, 2026
  98. D. Ben KnobleOct 27, 2026
  99. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 20, 2026
  100. D. Ben KnobleOct 24, 2026
  101. Harald NordgrenOct 25, 2026
  102. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 20, 2026
  103. D. Ben KnobleOct 24, 2026
  104. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 20, 2026
  105. D. Ben KnobleOct 24, 2026
  106. Harald NordgrenOct 25, 2026
  107. Junio C HamanoOct 23, 2026
  108. D. Ben KnobleOct 24, 2026
  109. Phillip WoodOct 26, 2026
  110. Junio C HamanoOct 26, 2026
  111. Harald NordgrenOct 27, 2026
  112. Phillip WoodOct 27, 2026
  113. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 25, 2026
  114. 1/5 fetch: add remote.<name>.refmapHarald Nordgren via GitGitGadget, Oct 25, 2026
  115. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 25, 2026
  116. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 25, 2026
  117. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 25, 2026
  118. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 25, 2026
  119. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 27, 2026
  120. 1/5 fetch: add remote.<name>.fetchRefmapHarald Nordgren via GitGitGadget, Oct 27, 2026
  121. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 27, 2026
  122. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 27, 2026
  123. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 27, 2026
  124. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 27, 2026
  125. 0/6 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Oct 30, 2026
  126. 1/6 fetch: add remote.<name>.fetchRefmapHarald Nordgren via GitGitGadget, Oct 30, 2026
  127. Phillip WoodNov 12, 2026
  128. Junio C HamanoNov 12, 2026
  129. Phillip WoodNov 13, 2026
  130. 2/6 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Oct 30, 2026
  131. 3/6 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Oct 30, 2026
  132. 4/6 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Oct 30, 2026
  133. 5/6 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Oct 30, 2026
  134. 6/6 remote: resolve @{push} through remote.<name>.fetchRefmapHarald Nordgren via GitGitGadget, Oct 30, 2026
  135. D. Ben KnobleNov 11, 2026
  136. Junio C HamanoNov 11, 2026
  137. Harald NordgrenNov 14, 2026
  138. Harald NordgrenNov 11, 2026
  139. Phillip WoodNov 11, 2026
  140. Junio C HamanoNov 11, 2026
  141. D. Ben KnobleNov 11, 2026
  142. Phillip WoodNov 12, 2026
  143. Matt HunterNov 12, 2026
  144. Phillip WoodNov 17, 2026
  145. 0/5 fetch: avoid fetching every branch of a new remote in a shallow repoHarald Nordgren via GitGitGadget, Nov 14, 2026
  146. 1/5 fetch: add remote.<name>.fetchRefmapHarald Nordgren via GitGitGadget, Nov 14, 2026
  147. Phillip WoodNov 17, 2026
  148. Junio C HamanoNov 17, 2026
  149. 2/5 fetch: extract collect_upstream_from_remote() helperHarald Nordgren via GitGitGadget, Nov 14, 2026
  150. 3/5 fetch: infer branches to fetch from a refmap-only remoteHarald Nordgren via GitGitGadget, Nov 14, 2026
  151. 4/5 remote: add "git remote add --limited-fetch"Harald Nordgren via GitGitGadget, Nov 14, 2026
  152. 5/5 remote: default to --limited-fetch in a shallow repositoryHarald Nordgren via GitGitGadget, Nov 14, 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.