Re: [PATCH v3] tracking branches: add advice to ambiguous refspec error

From: Tao Klerks <tao@klerks.biz>
Date: Mar 29, 2022, 11:26 UTC
Message-ID: <CAPMMpogK_e8Z3QobtJTnrzY=MynF0kqbZJEv=cZgWzwUodQx=A@mail.gmail.com>
In-Reply-To: <xmqqo81p256z.fsf@gitster.g>

OK, I

On Mon, Mar 28, 2022 at 10:27 PM Junio C Hamano <gitster@pobox.com> wrote:

>
> Small things accumulate.
>

OK. I've tried combining Junio's "only do something when needed" case statement with Glen's "co-locate advice-related string manipulations" proposal, and I believe this disqualifies and obviates the need for passing around any new "are we going to be issuing advice" flag.

$ 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.