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

Is there a quick way to identify commits that reference missing trees or blobs?

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 23, 2011, 16:48 UTC
Message-ID
<CAH3AnroyfeGOo_23nHKhLjxEnP_qEMi7as1UjXEFjjuVOckBjw@mail.gmail.com>

I was wondering if there is a quick way to identify commits that reference missing trees or blobs as identified by git fsck?

This would be quite useful in situations where one is trying to salvage as much history as possible from a damaged repository.

jon.
Next: Clemens Buchacher
Message 1 of 5 in “Is there a quick way to identify commits that reference missing trees or blobs?”
  1. Jon SeymourJul 23, 2011
  2. Clemens BuchacherJul 25, 2011
  3. Clemens BuchacherJul 25, 2011
  4. Jon SeymourJul 26, 2011
  5. Jon SeymourJul 26, 2011

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.