From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Benedek Kozma <cyberbeni@gmail.com>
Subject: Re: [PATCH v2] fetch: do not run a redundant fetch from submodule
Date: Tue, 17 May 2022 09:47:06 -0700 [thread overview]
Message-ID: <kl6lo7zwhzsl.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqk0alyqyj.fsf_-_@gitster.g>
This version looks good to me, thanks :)
Reviewed-by: Glen Choo <chooglen@google.com>
Junio C Hamano <gitster@pobox.com> writes:
> t5617 is much cleanly organized than t5526, and we may want to clean
> up the latter after dust settles.
Yeah, t5526 has so many tests for the 'core' functionality that it's
hard to fit something 'tangential' like "--all". I might touch it again
soon, so I'll keep this in mind.
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> index e3791f09ed..8b15c40bb2 100644
> --- a/builtin/fetch.c
> +++ b/builtin/fetch.c
> @@ -2261,7 +2265,17 @@ int cmd_fetch(int argc, const char **argv, const char *prefix)
> result = fetch_multiple(&list, max_children);
> }
>
> - if (!result && (recurse_submodules != RECURSE_SUBMODULES_OFF)) {
> +
> + /*
> + * This is only needed after fetch_one(), which does not fetch
> + * submodules by itself.
> + *
> + * When we fetch from multiple remotes, fetch_multiple() has
> + * already updated submodules to grab commits necessary for
> + * the fetched history from each remote, so there is no need
> + * to fetch submodules from here.
> + */
> + if (!result && remote && (recurse_submodules != RECURSE_SUBMODULES_OFF)) {
> struct strvec options = STRVEC_INIT;
> int max_children = max_jobs;
Looks good; the comment is easier to understand than my suggestion for
sure.
> diff --git a/t/t5526-fetch-submodules.sh b/t/t5526-fetch-submodules.sh
> index 43dada8544..a301b56db8 100755
> --- a/t/t5526-fetch-submodules.sh
> +++ b/t/t5526-fetch-submodules.sh
> @@ -1125,4 +1125,31 @@ test_expect_success 'fetch --recurse-submodules updates name-conflicted, unpopul
> )
> '
>
> +test_expect_success 'fetch --all with --recurse-submodules' '
> + test_when_finished "rm -fr src_clone" &&
> + git clone --recurse-submodules src src_clone &&
> + (
> + cd src_clone &&
> + git config submodule.recurse true &&
> + git config fetch.parallel 0 &&
> + git fetch --all 2>../fetch-log
> + ) &&
> + grep "^Fetching submodule sub$" fetch-log >fetch-subs &&
> + test_line_count = 1 fetch-subs
> +'
> +
> +test_expect_success 'fetch --all with --recurse-submodules with multiple' '
> + test_when_finished "rm -fr src_clone" &&
> + git clone --recurse-submodules src src_clone &&
> + (
> + cd src_clone &&
> + git remote add secondary ../src &&
> + git config submodule.recurse true &&
> + git config fetch.parallel 0 &&
> + git fetch --all 2>../fetch-log
> + ) &&
> + grep "Fetching submodule sub" fetch-log >fetch-subs &&
> + test_line_count = 2 fetch-subs
> +'
> +
Also looks good.
next prev parent reply other threads:[~2022-05-17 16:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:46 Bugreport - submodules are fetched twice in some cases Benedek Kozma
2022-04-29 17:39 ` Junio C Hamano
2022-04-29 19:05 ` Glen Choo
2022-04-29 20:02 ` Junio C Hamano
2022-04-29 20:37 ` Glen Choo
2022-05-14 0:07 ` Glen Choo
2022-05-14 5:24 ` Junio C Hamano
2022-05-16 17:45 ` Glen Choo
2022-05-16 18:25 ` Junio C Hamano
2022-05-16 19:04 ` Junio C Hamano
2022-05-16 21:53 ` [PATCH] fetch: do not run a redundant fetch from submodule Junio C Hamano
2022-05-16 22:56 ` Glen Choo
2022-05-16 23:33 ` Junio C Hamano
2022-05-16 23:53 ` [PATCH v2] " Junio C Hamano
2022-05-17 16:47 ` Glen Choo [this message]
2022-05-18 15:53 ` Junio C Hamano
2022-05-14 0:15 ` Bugreport - submodules are fetched twice in some cases Glen Choo
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kl6lo7zwhzsl.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=cyberbeni@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).