Re: [PATCH v11] checkout: extend --track with a "fetch" mode to refresh start-point

From: Junio C Hamano <gitster@pobox.com>
Date: May 21, 2026, 23:53 UTC
Message-ID: <xmqqzf1sxqu4.fsf@gitster.g>
In-Reply-To: <01526f43-86aa-466f-a1e8-054284e1a2e1@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

> Don't we want to avoid creating a branch with an ambiguous upstream so 
> that a subsequent "git pull" works though? Looking at 
> branch.c:setup_tracking() it seems to reject upstream branches that 
> match more than one remote.

Yes. We may try to avoid creating misconfigured branches in the first place, but we'd want to make sure other parts of the system that consumes existing branches to behave as sensible as possible, no?

Thanks.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.