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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 19, 2011, 19:28 UTC
Message-ID
<7vty4wmkdt.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20111219171055.GA21227@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Perhaps we should squash in the test below, which demonstrates the
> breakage. I also wonder if this is maint-worthy.

Thanks for a thorough analysis. I agree that this should go to maint even more so, as it fixes a case to push to a non-empty repository.

Previous: Jeff KingNext: Jeff King
Message 3 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.