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

Re: BUG: fetch in certain repo always gives "did not send all necessary objects"

From
Jeff King <peff@peff.net>
Date
Feb 7, 2018, 13:23 UTC
Message-ID
<20180207132304.GC16018@sigill.intra.peff.net>
In-Reply-To
<CACsJy8CUgmyw6Ug6wQEFaj9Ze45mZfRoE4J16zVv5usT791Kmw@mail.gmail.com>
On Wed, Feb 07, 2018 at 06:08:40PM +0700, Duy Nguyen wrote:
Show 8 quoted lines
> > And/or ideas of what steps could cause corruption so I can send out a
> > PSA to help users avoid it?
> 
> There is another thing we could do. One bad HEAD should not abort the
> entire operation (at least if it's not the current worktree's HEAD).
> We could still give a warning and move on, or don't warn at all and
> let "git worktree prune" collect it (which I see from your message
> that it also fails to do).

Whether that's safe or not depends very much on what the caller intends to do with the ref. Skipping broken refs in "git prune" is a bad idea, for instance.

-Peff
Previous: Duy NguyenNext: Elijah Newren
Message 5 of 10 in “BUG: fetch in certain repo always gives "did not send all necessary objects"”
  1. Elijah NewrenFeb 6, 2018
  2. Stefan BellerFeb 6, 2018
  3. Elijah NewrenFeb 7, 2018
  4. Duy NguyenFeb 7, 2018
  5. Jeff KingFeb 7, 2018
  6. Elijah NewrenFeb 7, 2018
  7. Jeff KingFeb 7, 2018
  8. Jeff KingFeb 7, 2018
  9. Elijah NewrenFeb 7, 2018
  10. Jeff KingFeb 7, 2018

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.