From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: "Tao Klerks via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Tao Klerks" <tao@klerks.biz>
Subject: Re: [PATCH v7] tracking branches: add advice to ambiguous refspec error
Date: Fri, 01 Apr 2022 12:57:37 -0700 [thread overview]
Message-ID: <xmqqy20ovaoe.fsf@gitster.g> (raw)
In-Reply-To: <kl6lmth4sq1m.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Fri, 01 Apr 2022 09:53:57 -0700")
Glen Choo <chooglen@google.com> writes:
> "Tao Klerks via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> diff --git a/branch.c b/branch.c
>> index 6b31df539a5..182f1c5a556 100644
>> --- a/branch.c
>> +++ b/branch.c
>> @@ -18,17 +18,31 @@ struct tracking {
>> int matches;
>> };
>>
>> +struct find_tracked_branch_cb {
>> + struct tracking *tracking;
>> + struct string_list ambiguous_remotes;
>> +};
>> +
>> static int find_tracked_branch(struct remote *remote, void *priv)
>> {
>> - struct tracking *tracking = priv;
>> + struct find_tracked_branch_cb *ftb = priv;
>> + struct tracking *tracking = ftb->tracking;
>>
>> if (!remote_find_tracking(remote, &tracking->spec)) {
>> - if (++tracking->matches == 1) {
>> + switch (++tracking->matches) {
>> + case 1:
>> string_list_append(tracking->srcs, tracking->spec.src);
>> tracking->remote = remote->name;
>> - } else {
>> + break;
>> + case 2:
>> + /* there are at least two remotes; backfill the first one */
>> + string_list_append(&ftb->ambiguous_remotes, tracking->remote);
>> + /* fall through */
>> + default:
>> + string_list_append(&ftb->ambiguous_remotes, remote->name);
>> free(tracking->spec.src);
>> string_list_clear(tracking->srcs, 0);
>> + break;
>> }
>> tracking->spec.src = NULL;
>> }
>
> Ah I see, on the first iteration, we set the first remote's name to
> tracking->remote, and on the second iteration, we copy that value to the
> list before copying the _current_ remote's name to the list.
>
>> -test_expect_success 'avoid ambiguous track' '
>> +test_expect_success 'avoid ambiguous track and advise' '
>> git config branch.autosetupmerge true &&
>> git config remote.ambi1.url lalala &&
>> git config remote.ambi1.fetch refs/heads/lalala:refs/heads/main &&
>> git config remote.ambi2.url lilili &&
>> git config remote.ambi2.fetch refs/heads/lilili:refs/heads/main &&
>> - test_must_fail git branch all1 main &&
>> + cat <<-EOF >expected &&
>> + fatal: not tracking: ambiguous information for ref '\''refs/heads/main'\''
>> + hint: There are multiple remotes whose fetch refspecs map to the remote
>> + hint: tracking ref '\''refs/heads/main'\'':
>> + hint: ambi1
>> + hint: ambi2
>> + hint: ''
>> + hint: This is typically a configuration error.
>> + hint: ''
>> + hint: To support setting up tracking branches, ensure that
>> + hint: different remotes'\'' fetch refspecs map into different
>> + hint: tracking namespaces.
>> + EOF
>> + test_must_fail git branch all1 main 2>actual &&
>> + test_cmp expected actual &&
>> test -z "$(git config branch.all1.merge)"
>> '
>
> And this test shows that this indeed does what we think it does. Nicely
> done.
>
> I notice that we there is an instance of test -z "$(some git command)",
> which IIRC is discouraged because it would mask a failure in the git
> command, but that's not new and I don't think it needs to be fixed in
> this series anyway.
>
> Reviewed-by: Glen Choo <chooglen@google.com>
Thanks for giving the patch a careful read.
Will queue.
Thanks.
prev parent reply other threads:[~2022-04-01 19:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:23 [PATCH] tracking branches: add advice to ambiguous refspec error Tao Klerks via GitGitGadget
2022-03-21 14:11 ` Ævar Arnfjörð Bjarmason
2022-03-22 9:09 ` Tao Klerks
2022-03-22 9:18 ` [PATCH v2] RFC: " Tao Klerks via GitGitGadget
2022-03-22 10:04 ` Ævar Arnfjörð Bjarmason
2022-03-28 6:51 ` [PATCH v3] " Tao Klerks via GitGitGadget
2022-03-28 16:23 ` Junio C Hamano
2022-03-28 17:12 ` Glen Choo
2022-03-28 17:23 ` Junio C Hamano
2022-03-28 18:02 ` Tao Klerks
2022-03-28 18:50 ` Ævar Arnfjörð Bjarmason
2022-03-28 20:32 ` Junio C Hamano
2022-03-28 20:27 ` Junio C Hamano
2022-03-29 11:26 ` Tao Klerks
2022-03-29 11:26 ` [PATCH v4] " Tao Klerks via GitGitGadget
2022-03-29 11:31 ` Tao Klerks
2022-03-29 15:49 ` Junio C Hamano
2022-03-30 4:17 ` Tao Klerks
2022-03-30 7:20 ` [PATCH v5] " Tao Klerks via GitGitGadget
2022-03-30 13:19 ` Ævar Arnfjörð Bjarmason
2022-03-30 14:23 ` Tao Klerks
2022-03-30 15:18 ` Tao Klerks
2022-03-30 17:14 ` Ævar Arnfjörð Bjarmason
2022-03-30 20:37 ` Junio C Hamano
2022-03-30 21:09 ` Ævar Arnfjörð Bjarmason
2022-03-30 22:07 ` Junio C Hamano
2022-03-30 22:51 ` Ævar Arnfjörð Bjarmason
2022-03-31 16:01 ` [PATCH v6] " Tao Klerks via GitGitGadget
2022-03-31 19:32 ` Junio C Hamano
2022-03-31 23:57 ` Glen Choo
2022-04-01 4:30 ` Tao Klerks
2022-04-01 16:41 ` Glen Choo
2022-03-31 19:33 ` Junio C Hamano
2022-04-01 6:05 ` [PATCH v7] " Tao Klerks via GitGitGadget
2022-04-01 16:53 ` Glen Choo
2022-04-01 19:57 ` 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
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=xmqqy20ovaoe.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=tao@klerks.biz \
/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).