Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Phillip Wood <phillip.wood123@gmail.com>,
	 "D. Ben Knoble" <ben.knoble@gmail.com>,
	 Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH v8 2/5] fetch: extract collect_upstream_from_remote() helper
Date: Sat, 10 Oct 2026 10:11:39 -0700	[thread overview]
Message-ID: <xmqqik39iipg.fsf@gitster.g> (raw)
In-Reply-To: <08fea07a8be8a91ac54db44f9c035ecb49c86c9f.1791619334.git.gitgitgadget@gmail.com> (Harald Nordgren via GitGitGadget's message of "Sat, 10 Oct 2026 08:02:11 +0000")

"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:

> @@ -1962,23 +1962,36 @@ static int do_fetch(struct transport *transport,
>  
>  	if (rs->nr) {
>  		refspec_ref_prefixes(rs, &transport_ls_refs_options.ref_prefixes);
>  	} else {
> -		struct branch *branch = branch_get(NULL);
>  
> -		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 (branch && branch_has_merge_config(branch) &&
> -		    !strcmp(branch->remote_name, transport->remote->name)) {
> -			int i;
> -			for (i = 0; i < branch->merge_nr; i++) {
> -				strvec_push(&transport_ls_refs_options.ref_prefixes,
> -					    branch->merge[i]->src);
> -			}
> -		}
>  
>  		/*
>  		 * If there are no refs specified to fetch, then we just

We used to say "if there is remote.*.fetch, add them.  whether there
is remote.*.fetch or not, if the current branch builds on their
branch(es), add them too".

> @@ -1962,23 +1962,36 @@ 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 string_list tracked = STRING_LIST_INIT_DUP;
> +		struct string_list_item *item;
>  
> +		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);

This reorganizes it to say "if there is remote.*.fetch, do the same
as before.  If there is not remote.*.fetch, add their branch(es) the
current branch wants".

This "duplicate what happens to the current branch" belongs to the
next step where you want to add more logic to the latter part (i.e.,
"no remote.*.fetch" case), and not to this step.

IOW I would have expected to see

	} 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);
	}

that touches "help the current branch when rs->nr == 0" part and
nothing else.

Of course, because the next step [3/5] wants to split the above
else{} block to do different things between the case where
remote.*.fetch is and is not empty, at that point the extra
code may be introduced there, ending up with the shape of if/else if
cascade as we see in your patch.

> diff --git a/remote.c b/remote.c
> index 99a086ea5a..5e980625b8 100644
> --- a/remote.c
> +++ b/remote.c
> @@ -1884,6 +1884,21 @@ int branch_merge_matches(struct branch *branch,
>  	return refname_match(branch->merge[i]->src, refname);
>  }
>  
> +void collect_upstream_from_remote(struct repository *repo,
> +				   struct string_list *tracked,
> +				   struct remote *remote,
> +				   const char *refname)
> +{
> +	struct branch *branch = repo_branch_get(repo, refname);
> +
> +	if (!branch_has_merge_config(branch) ||
> +	    strcmp(branch->remote_name, remote->name))
> +		return;
> +	for (int i = 0; i < branch->merge_nr; i++)
> +		string_list_insert(tracked, branch->merge[i]->src);
> +}

The original tries to avoid branch == NULL causing a segfault, but
the above does not.  Intended or overlooked?

Other than that, this looks like a straight-forward refactoring.

  reply	other threads:[~2026-10-10 17:11 UTC|newest]

Thread overview: 63+ 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 [this message]
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

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=xmqqik39iipg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --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