From: Junio C Hamano Date: Thu, 31 Mar 2022 19:33:51 GMT Subject: Re: [PATCH v6] tracking branches: add advice to ambiguous refspec error Message-ID: In-Reply-To: "Tao Klerks via GitGitGadget" writes: > From: Tao Klerks > > The error "not tracking: ambiguous information for ref" is raised > when we are evaluating what tracking information to set on a branch, > and find that the ref to be added as tracking branch is mapped > under multiple remotes' fetch refspecs. > > This can easily happen when a user copy-pastes a remote definition > in their git config, and forgets to change the tracking path. > > Add advice in this situation, explicitly highlighting which remotes > are involved and suggesting how to correct the situation. > ... > Documentation/config/advice.txt | 4 +++ > advice.c | 1 + > advice.h | 1 + > branch.c | 63 +++++++++++++++++++++++++++++---- > 4 files changed, 62 insertions(+), 7 deletions(-) Can we add a test case for the new "advice" output? Thanks.