From: Junio C Hamano <gitster@pobox.com>
To: Daniel Black <daniel@mariadb.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] submodule: correct remote name with fetch
Date: Wed, 09 Oct 2024 10:51:40 -0700 [thread overview]
Message-ID: <xmqqv7y1tb9v.fsf@gitster.g> (raw)
In-Reply-To: <20241009033257.1316690-1-daniel@mariadb.org> (Daniel Black's message of "Wed, 9 Oct 2024 14:32:54 +1100")
Daniel Black <daniel@mariadb.org> writes:
> The code fetches the submodules remote based on the superproject remote name
> instead of the submodule remote name[1].
>
> Instead of grabbing the default remote of the superproject repository, ask
> the default remote of the submodule we are going to run 'git fetch' in.
>
> 1. https://lore.kernel.org/git/ZJR5SPDj4Wt_gmRO@pweza/
>
> Signed-off-by: Daniel Black <daniel@mariadb.org>
> ---
> builtin/submodule--helper.c | 9 ++++++++-
> t/t5572-pull-submodule.sh | 20 ++++++++++++++++++++
> 2 files changed, 28 insertions(+), 1 deletion(-)
Excellent. Will queue.
Thanks.
> diff --git a/t/t5572-pull-submodule.sh b/t/t5572-pull-submodule.sh
> index 916e58c166..9b6cf8d88b 100755
> --- a/t/t5572-pull-submodule.sh
> +++ b/t/t5572-pull-submodule.sh
> @@ -230,6 +230,7 @@ test_expect_success 'branch has no merge base with remote-tracking counterpart'
>
> test_create_repo a-submodule &&
> test_commit -C a-submodule foo &&
> + test_commit -C a-submodule bar &&
>
> test_create_repo parent &&
> git -C parent submodule add "$(pwd)/a-submodule" &&
> @@ -246,4 +247,23 @@ test_expect_success 'branch has no merge base with remote-tracking counterpart'
> git -C child pull --recurse-submodules --rebase
> '
>
> +test_expect_success 'fetch submodule remote of different name from superproject' '
> + git -C child remote rename origin o1 &&
> + git -C child submodule update --init &&
> +
> + # Needs to create unreachable commit from current master branch.
> + git -C a-submodule checkout -b newmain HEAD^ &&
> + test_commit -C a-submodule echo &&
> + test_commit -C a-submodule moreecho &&
> + subc=$(git -C a-submodule rev-parse --short HEAD) &&
> +
> + git -C parent/a-submodule fetch &&
> + git -C parent/a-submodule checkout "$subc" &&
> + git -C parent commit -m "update submodule" a-submodule &&
> + git -C a-submodule reset --hard HEAD^^ &&
> +
> + git -C child pull --no-recurse-submodules &&
> + git -C child submodule update
> +'
> +
> test_done
prev parent reply other threads:[~2024-10-09 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 11:09 bug: submodule update fails to fetch Sergei Golubchik
2023-06-22 13:07 ` Taylor Blau
2023-06-22 16:39 ` Sergei Golubchik
2023-06-23 7:26 ` Jacob Keller
2024-10-01 7:24 ` [PATCH] submodule: correct remote name with fetch Daniel Black
2024-10-01 17:27 ` Junio C Hamano
2024-10-01 17:34 ` Junio C Hamano
2024-10-08 1:49 ` Daniel Black
2024-10-08 1:49 ` [RFC PATCH v2] submodule: correct remote name with fetch Daniel Black
2024-10-08 19:23 ` Junio C Hamano
2024-10-09 3:32 ` [PATCH v3] " Daniel Black
2024-10-09 17:51 ` Junio C Hamano [this message]
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=xmqqv7y1tb9v.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=daniel@mariadb.org \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).