"Tao Klerks via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > From: Tao Klerks <tao@xxxxxxxxxx> > > 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. > > Signed-off-by: Tao Klerks <tao@xxxxxxxxxx> > --- > tracking branches: add advice to ambiguous refspec error > > I believe this third version incorporates all Ævar's suggestions, and > might be usable. Removed "RFC" prefix. > > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1183%2FTaoK%2Fadvise-ambiguous-tracking-refspec-v4 > Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1183/TaoK/advise-ambiguous-tracking-refspec-v4 > Pull-Request: https://github.com/gitgitgadget/git/pull/1183 > > Range-diff vs v3: > > 1: 22ffe81ac26 = 1: ac6c782f566 tracking branches: add advice to ambiguous refspec error > > > Documentation/config/advice.txt | 4 +++ > advice.c | 1 + > advice.h | 1 + > branch.c | 44 +++++++++++++++++++++++++++++---- > 4 files changed, 45 insertions(+), 5 deletions(-) Sent a wrong version? The patch text seems to be identical to that of v3 message archived at https://lore.kernel.org/git/pull.1183.v3.git.1648450268285.gitgitgadget@xxxxxxxxx/
