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

Re: [PATCH] fsck: do not crash on tag objects which do not contain an empty line

From
Nicolas Pitre <nico@cam.org>
Date
Jun 8, 2007, 02:04 UTC
Message-ID
<alpine.LFD.0.99.0706072158160.12885@xanadu.home>
In-Reply-To
<200706080128.48637.johan@herland.net>
On Fri, 8 Jun 2007, Johan Herland wrote:
Show 7 quoted lines
> I agree that we should fail gracefully, and my code is clearly not doing 
> that in this case. My bad.
> 
> But the code should also detect invalid tag objects, and in this case I'm 
> not yet convinced that the tag object causing the failure is in fact valid. 
> If someone can convince me that the blank line after headers is optional, 
> then I'll gladly fix the code.
That's irrelevant.
Because you are fed invalid data is no excuse for crashing.

Especially in a tool like fsck, you should _expect_ and cope with invalid data. That's why it exists in the first place: to identify such data.

Nicolas
Previous: Johannes SchindelinNext: Johan Herland
Message 6 of 10 in “fsck: do not crash on tag objects which do not contain an empty line”
  1. fsck: do not crash on tag objects which do not contain an empty lineJohannes Schindelin, Jun 7, 2007
  2. Johan HerlandJun 7, 2007
  3. Johannes SchindelinJun 7, 2007
  4. Johan HerlandJun 7, 2007
  5. Johannes SchindelinJun 7, 2007
  6. Nicolas PitreJun 8, 2007
  7. Johan HerlandJun 8, 2007
  8. Junio C HamanoJun 8, 2007
  9. Johannes SchindelinJun 8, 2007
  10. Andy ParkinsJun 8, 2007

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.