git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] remote-curl: don't pass back fake refs

From
Jeff King <peff@peff.net>
Date
Dec 19, 2011, 21:29 UTC
Message-ID
<20111219212932.GA18743@sigill.intra.peff.net>
In-Reply-To
<7v39cgmety.fsf@alter.siamese.dyndns.org>
On Mon, Dec 19, 2011 at 01:28:09PM -0800, Junio C Hamano wrote:
Show 10 quoted lines
> > Do you want to squash in those tests, or should I re-send with a commit
> > message more fully explaining the situation?
> 
> I was lazy and added these three lines at the end:
> 
>     This also fixes pushing with --mirror to a smart-http remote that uses
>     alternates. The fake ".have" refs the server gives to avoid unnecessary
>     network transfer has a similar bad interactions with the machinery.
> 
> but it may warrant a more thorough write-up there.

I think that's probably enough. I could restructure the whole text to talk less about capabilities^{} and more about generically preventing fake refs, but I really don't think there's much point.

-Peff
Previous: Junio C Hamano
Message 6 of 6 in “remote-curl: don't pass back fake refs”
  1. remote-curl: don't pass back fake refsJeff King, Dec 17, 2011
  2. Jeff KingDec 19, 2011
  3. Junio C HamanoDec 19, 2011
  4. Jeff KingDec 19, 2011
  5. Junio C HamanoDec 19, 2011
  6. Jeff KingDec 19, 2011

Read the whole thread, see it on lore, or plain text.

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