Re: [PATCH v2 3/3] transport.c: introduce core.alternateRefsPrefixes

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 24, 2018, 21:55 UTC
Message-ID: <xmqqva6ur24y.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180924205022.GA26936@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> Do you have an opinion on whether for_each_alternate_refs() interface
> should stop passing back refnames? By the "they may not even exist"
> rationale in this sub-thread, I think it's probably foolish for any
> caller to actually depend on the names being meaningful.

I personally do not mind they were all ".have" or unnamed.

The primary motivatgion behind for-each-alternate-refs was that we wanted to find more anchoring points to help the common ancestry negotiation and for-each-*-ref was the obvious way to do so; the user did not care anything about names.

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