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

Re: git fsck messages - what to do about it?

From
Junio C Hamano <junkio@cox.net>
Date
Sep 18, 2005, 22:13 UTC
Message-ID
<7vfys210tm.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.58.0509181435190.9106@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> So using "--unreachable" gives much more raw data, but it usually tends to
> hide the real _information_, and the end result is thus much harder to
> understand.

Yup. That's exactly why the 'git-lost-found' sample script given in <7vll1xndxi.fsf@assigned-by-dhcp.cox.net> runs git-fsck-objects output without --unreachable.

Previous: Linus Torvalds
Message 9 of 9 in “git fsck messages - what to do about it?”
  1. Wolfgang DenkSep 16, 2005
  2. Catalin MarinasSep 16, 2005
  3. Wolfgang DenkSep 16, 2005
  4. Junio C HamanoSep 16, 2005
  5. Petr BaudisSep 16, 2005
  6. Linus TorvaldsSep 16, 2005
  7. Linus TorvaldsSep 16, 2005
  8. Linus TorvaldsSep 18, 2005
  9. Junio C HamanoSep 18, 2005

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.