From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Tao Klerks <tao@klerks.biz>
Subject: tk/ambiguous-fetch-refspec (was: What's cooking in git.git (Mar 2022, #07; Wed, 30))
Date: Thu, 31 Mar 2022 11:47:35 +0200 [thread overview]
Message-ID: <220331.864k3esb9d.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee2i50h9.fsf@gitster.g>
On Wed, Mar 30 2022, Junio C Hamano wrote:
> * tk/ambiguous-fetch-refspec (2022-03-28) 1 commit
> - tracking branches: add advice to ambiguous refspec error
>
> Give hint when branch tracking cannot be established because fetch
> refspecs from multiple remote repositories overlap.
>
> Will merge to 'next'?
> source: <pull.1183.v3.git.1648450268285.gitgitgadget@gmail.com>
If it helps: Reviewed-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
I've been the primary reviewer of this topic, and it looks good to me in
its current shape.
next prev parent reply other threads:[~2022-03-31 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 2:17 What's cooking in git.git (Mar 2022, #07; Wed, 30) Junio C Hamano
2022-03-31 9:41 ` jh/p4-various-fixups (was: What's cooking in git.git (Mar 2022, #07; Wed, 30)) Ævar Arnfjörð Bjarmason
2022-04-01 14:29 ` Joel Holdsworth
2022-03-31 9:45 ` ab/commit-plug-leaks " Ævar Arnfjörð Bjarmason
2022-03-31 9:47 ` Ævar Arnfjörð Bjarmason [this message]
2022-03-31 9:57 ` ab/ci-setup-simplify + ab/ci-github-workflow-markup " Ævar Arnfjörð Bjarmason
2022-03-31 14:51 ` rc/fetch-refetch " Robert Coup
2022-03-31 16:55 ` What's cooking in git.git (Mar 2022, #07; Wed, 30) Glen Choo
2022-04-03 20:05 ` Philippe Blain
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=220331.864k3esb9d.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.