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

Re: Possible regression: lost diagnostic message when pushing non-commit objects to refs/heads/*

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 24, 2025, 03:37 UTC
Message-ID
<xmqqikdwo8i1.fsf@gitster.g>
In-Reply-To
<CABPp-BGL2tJR4dPidQuFcp-X0_VkVTknCY-0Zgo=jHVGv_P=wA@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 14 quoted lines
> Bisecting shows that this
> started with commit 9d2962a7c44 ("receive-pack: use batched reference
> updates", 2025-05-19).  That commit message to me suggests that while
> error handling was necessarily changed, that dropping the errors was
> not intentional:
>
> ```
> As using batched updates requires the error handling to be moved to the
> end of the flow, create and use a 'struct strset' to track the failed
> refs and attribute the correct errors to them.
> ```
>
> But it's possible I'm reading it wrong.  Was it intentional, or is
> this a regression?

The topic bisect found was supposed to be purely performance optimization, and we should take any changes in behaviour as regressions.

Thanks.
Previous: Elijah NewrenNext: Jeff King
Message 2 of 6 in “Possible regression: lost diagnostic message when pushing non-commit objects to refs/heads/*”
  1. Elijah NewrenDec 24, 2025
  2. Junio C HamanoDec 24, 2025
  3. Jeff KingDec 24, 2025
  4. Jeff KingDec 24, 2025
  5. Karthik NayakDec 26, 2025
  6. Jeff KingDec 27, 2025

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.