From: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Phillip Wood <phillip.wood123@gmail.com>,
"D. Ben Knoble" <ben.knoble@gmail.com>,
Harald Nordgren <haraldnordgren@gmail.com>
Subject: [PATCH v9 0/5] fetch: avoid fetching every branch of a new remote in a shallow repo
Date: Wed, 14 Oct 2026 07:04:07 +0000 [thread overview]
Message-ID: <pull.2412.v9.git.git.1791961452.gitgitgadget@gmail.com> (raw)
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 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>.refmap
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 | 8 +++
Documentation/fetch-options.adoc | 5 ++
Documentation/git-remote.adoc | 14 +++-
builtin/fetch.c | 84 ++++++++++++++++++----
builtin/remote.c | 31 ++++++--
remote.c | 51 ++++++++++++-
remote.h | 19 +++++
t/meson.build | 1 +
t/t5505-remote.sh | 76 ++++++++++++++++++++
t/t5510-fetch.sh | 63 ++++++++++++++++
t/t5586-fetch-refmap.sh | 119 +++++++++++++++++++++++++++++++
11 files changed, 448 insertions(+), 23 deletions(-)
create mode 100755 t/t5586-fetch-refmap.sh
base-commit: 6de20f6092dcf9bdb1c8efe03db4b70c82b423dd
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2412%2FHaraldNordgren%2Ffetch-shallow-narrow-refspec-v9
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2412/HaraldNordgren/fetch-shallow-narrow-refspec-v9
Pull-Request: https://github.com/git/git/pull/2412
Range-diff vs v8:
1: 2a48c21bc8 = 1: 2a48c21bc8 fetch: add remote.<name>.refmap
2: 08fea07a8b ! 2: 50382bce7e fetch: extract collect_upstream_from_remote() helper
@@ Commit message
## builtin/fetch.c ##
@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
-
if (rs->nr) {
refspec_ref_prefixes(rs, &transport_ls_refs_options.ref_prefixes);
-+ } else if (transport->remote->fetch.nr) {
-+ struct string_list tracked = STRING_LIST_INIT_DUP;
-+ struct string_list_item *item;
-+
-+ refspec_ref_prefixes(&transport->remote->fetch,
-+ &transport_ls_refs_options.ref_prefixes);
-+ if (follow_remote_head != FOLLOW_REMOTE_NEVER)
-+ do_set_head = 1;
-+
-+ /*
-+ * The configured refspec may not cover the current
-+ * branch's upstream (e.g. a narrowed -t refspec), so
-+ * make sure we can still fetch it regardless.
-+ */
-+ collect_upstream_from_remote(the_repository, &tracked,
-+ transport->remote, NULL);
-+ for_each_string_list_item(item, &tracked)
-+ strvec_push(&transport_ls_refs_options.ref_prefixes,
-+ item->string);
-+ string_list_clear(&tracked, 0);
} else {
- struct branch *branch = branch_get(NULL);
+ struct string_list tracked = STRING_LIST_INIT_DUP;
+ struct string_list_item *item;
-- if (transport->remote->fetch.nr) {
-- refspec_ref_prefixes(&transport->remote->fetch,
-- &transport_ls_refs_options.ref_prefixes);
-- if (follow_remote_head != FOLLOW_REMOTE_NEVER)
-- do_set_head = 1;
-- }
+ if (transport->remote->fetch.nr) {
+ refspec_ref_prefixes(&transport->remote->fetch,
+@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
+ if (follow_remote_head != FOLLOW_REMOTE_NEVER)
+ do_set_head = 1;
+ }
- if (branch && branch_has_merge_config(branch) &&
- !strcmp(branch->remote_name, transport->remote->name)) {
- int i;
@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
- branch->merge[i]->src);
- }
- }
++
++ /*
++ * The configured refspec may not cover the current
++ * branch's upstream (e.g. a narrowed -t refspec), so
++ * make sure we can still fetch it regardless.
++ */
+ collect_upstream_from_remote(the_repository, &tracked,
+ transport->remote, NULL);
+ for_each_string_list_item(item, &tracked)
3: a39316d233 ! 3: 9ad8ad3eb4 fetch: infer branches to fetch from a refmap-only remote
@@ builtin/fetch.c: static struct ref *get_ref_map(struct remote *remote,
}
@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
+
+ if (rs->nr) {
+ refspec_ref_prefixes(rs, &transport_ls_refs_options.ref_prefixes);
+- } else {
++ } else if (transport->remote->fetch.nr) {
+ struct string_list tracked = STRING_LIST_INIT_DUP;
+ struct string_list_item *item;
+
+- if (transport->remote->fetch.nr) {
+- refspec_ref_prefixes(&transport->remote->fetch,
+- &transport_ls_refs_options.ref_prefixes);
+- if (follow_remote_head != FOLLOW_REMOTE_NEVER)
+- do_set_head = 1;
+- }
++ refspec_ref_prefixes(&transport->remote->fetch,
++ &transport_ls_refs_options.ref_prefixes);
++ if (follow_remote_head != FOLLOW_REMOTE_NEVER)
++ do_set_head = 1;
+
+ /*
+ * The configured refspec may not cover the current
+@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
+ strvec_push(&transport_ls_refs_options.ref_prefixes,
item->string);
string_list_clear(&tracked, 0);
- } else {
++ } else {
+ /*
+ * The --refmap command line option, if given, takes
+ * precedence over remote.<name>.refmap.
+ */
+ struct refspec *effective_refmap = refmap.nr ? &refmap :
+ &transport->remote->refmap;
- struct string_list tracked = STRING_LIST_INIT_DUP;
- struct string_list_item *item;
-
-- collect_upstream_from_remote(the_repository, &tracked,
-- transport->remote, NULL);
++ struct string_list tracked = STRING_LIST_INIT_DUP;
++ struct string_list_item *item;
++
+ if (effective_refmap->nr) {
+ branches_tracking_remote(the_repository,
+ transport->remote, &tracked);
@@ builtin/fetch.c: static int do_fetch(struct transport *transport,
+ collect_upstream_from_remote(the_repository, &tracked,
+ transport->remote, NULL);
+ }
- for_each_string_list_item(item, &tracked)
- strvec_push(&transport_ls_refs_options.ref_prefixes,
- item->string);
++ for_each_string_list_item(item, &tracked)
++ strvec_push(&transport_ls_refs_options.ref_prefixes,
++ item->string);
++ string_list_clear(&tracked, 0);
+
+ /*
+ * If there are no refs specified to fetch, then we just
## remote.c ##
@@ remote.c: void collect_upstream_from_remote(struct repository *repo,
4: 2b974bbe0a = 4: 75169f668e remote: add "git remote add --limited-fetch"
5: db27c29086 = 5: 9ee090d3d0 remote: default to --limited-fetch in a shallow repository
--
gitgitgadget
next prev parent reply other threads:[~2026-10-14 7:04 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 14:47 [PATCH] fetch: add config to avoid fetching every branch in shallow repo Harald Nordgren via GitGitGadget
2026-09-21 13:28 ` Phillip Wood
2026-09-21 21:45 ` Harald Nordgren
2026-09-22 13:00 ` Harald Nordgren
2026-09-22 14:53 ` Phillip Wood
2026-09-22 15:37 ` Harald Nordgren
2026-09-23 15:14 ` Phillip Wood
2026-09-22 17:11 ` Junio C Hamano
2026-09-22 21:40 ` Harald Nordgren
2026-09-23 15:19 ` Phillip Wood
2026-09-23 15:34 ` Junio C Hamano
2026-09-23 16:55 ` D. Ben Knoble
2026-09-23 19:50 ` Junio C Hamano
2026-09-24 17:10 ` D. Ben Knoble
2026-09-24 18:02 ` Junio C Hamano
2026-09-23 20:35 ` [PATCH v2] fetch: avoid fetching every branch of a new remote in a " Harald Nordgren via GitGitGadget
2026-09-23 21:38 ` Junio C Hamano
2026-09-25 10:49 ` [PATCH v3 0/4] " Harald Nordgren via GitGitGadget
2026-09-25 10:49 ` [PATCH v3 1/4] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-09-25 22:38 ` Junio C Hamano
2026-09-25 10:50 ` [PATCH v3 2/4] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-09-25 23:26 ` Junio C Hamano
2026-09-25 10:50 ` [PATCH v3 3/4] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-09-25 10:50 ` [PATCH v3 4/4] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-09-29 9:19 ` [PATCH v4 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo Harald Nordgren via GitGitGadget
2026-09-29 9:19 ` [PATCH v4 1/4] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-09-29 9:19 ` [PATCH v4 2/4] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-09-29 9:27 ` Harald Nordgren
2026-09-29 20:17 ` Junio C Hamano
2026-09-29 9:19 ` [PATCH v4 3/4] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-09-29 9:19 ` [PATCH v4 4/4] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-09-29 19:36 ` [PATCH v4 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo Junio C Hamano
2026-10-02 7:13 ` [PATCH v5 " Harald Nordgren via GitGitGadget
2026-10-02 7:13 ` [PATCH v5 1/4] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-10-02 7:13 ` [PATCH v5 2/4] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-10-02 7:13 ` [PATCH v5 3/4] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-10-02 16:28 ` Junio C Hamano
2026-10-02 7:13 ` [PATCH v5 4/4] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-10-04 8:31 ` [PATCH v6 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo Harald Nordgren via GitGitGadget
2026-10-04 8:31 ` [PATCH v6 1/4] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-10-04 8:31 ` [PATCH v6 2/4] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-10-04 8:31 ` [PATCH v6 3/4] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-10-04 8:31 ` [PATCH v6 4/4] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-10-04 17:17 ` [PATCH v6 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo Junio C Hamano
2026-10-04 19:51 ` Harald Nordgren
2026-10-05 12:17 ` Junio C Hamano
2026-10-05 18:09 ` Harald Nordgren
2026-10-07 21:56 ` [PATCH v7 " Harald Nordgren via GitGitGadget
2026-10-07 21:56 ` [PATCH v7 1/4] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-10-07 21:56 ` [PATCH v7 2/4] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-10-08 16:59 ` Junio C Hamano
2026-10-09 7:05 ` Harald Nordgren
2026-10-09 8:09 ` Harald Nordgren
2026-10-07 21:56 ` [PATCH v7 3/4] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-10-07 21:56 ` [PATCH v7 4/4] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-10-10 8:02 ` [PATCH v8 0/5] fetch: avoid fetching every branch of a new remote in a shallow repo Harald Nordgren via GitGitGadget
2026-10-10 8:02 ` [PATCH v8 1/5] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-10-10 8:02 ` [PATCH v8 2/5] fetch: extract collect_upstream_from_remote() helper Harald Nordgren via GitGitGadget
2026-10-10 17:11 ` Junio C Hamano
2026-10-10 18:36 ` Harald Nordgren
2026-10-10 8:02 ` [PATCH v8 3/5] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-10-10 8:02 ` [PATCH v8 4/5] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-10-10 17:16 ` Junio C Hamano
2026-10-10 8:02 ` [PATCH v8 5/5] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
2026-10-14 7:04 ` Harald Nordgren via GitGitGadget [this message]
2026-10-14 7:04 ` [PATCH v9 1/5] fetch: add remote.<name>.refmap Harald Nordgren via GitGitGadget
2026-10-14 7:04 ` [PATCH v9 2/5] fetch: extract collect_upstream_from_remote() helper Harald Nordgren via GitGitGadget
2026-10-14 7:04 ` [PATCH v9 3/5] fetch: infer branches to fetch from a refmap-only remote Harald Nordgren via GitGitGadget
2026-10-14 7:04 ` [PATCH v9 4/5] remote: add "git remote add --limited-fetch" Harald Nordgren via GitGitGadget
2026-10-14 7:04 ` [PATCH v9 5/5] remote: default to --limited-fetch in a shallow repository Harald Nordgren via GitGitGadget
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=pull.2412.v9.git.git.1791961452.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
--cc=phillip.wood123@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox