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

Re: [PATCH v2] make pack-objects a bit more resilient to repo corruption

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 22, 2010, 21:59 UTC
Message-ID
<7v4ocdlwhm.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.00.1010221714450.2764@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
> Yes, only the first one, ...
> ...  Comprehensive reporting is the job of 
> fsck.

I had the same knee-jerk reaction, and about to suggest using one bit from flags, but I agree the design balance you struck here is a good one.

Thanks.
Previous: Nicolas PitreNext: Geert Bosch
Message 9 of 11 in “make pack-objects a bit more resilient to repo corruption”
  1. make pack-objects a bit more resilient to repo corruptionNicolas Pitre, Oct 22, 2010
  2. Jeff KingOct 22, 2010
  3. Drew NorthupOct 22, 2010
  4. Nicolas PitreOct 22, 2010
  5. Nicolas PitreOct 22, 2010
  6. make pack-objects a bit more resilient to repo corruptionNicolas Pitre, Oct 22, 2010
  7. Sverre RabbelierOct 22, 2010
  8. Nicolas PitreOct 22, 2010
  9. Junio C HamanoOct 22, 2010
  10. Geert BoschOct 24, 2010
  11. Nicolas PitreOct 24, 2010

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.