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

Question about fsck-objects output

From
LSLarry Streepy <larry@lightspeed.com>
Date
Jan 25, 2007, 18:22 UTC
Message-ID
<45B8F575.5050106@lightspeed.com>

Sorry to ask such a basic question, but I can't quite decipher the output of fsck-objects. When I run it, I get this:

  git fsck-objects
dangling commit 2213f6d4dd39ca8baebd0427723723e63208521b
dangling commit f0d4e00196bd5ee54463e9ea7a0f0e8303da767f
dangling blob 6a6d0b01b3e96d49a8f2c7addd4ef8c3bd1f5761

Even after a "repack -a -d" they still exist. The man page has a short explanation, but, at least for me, it wasn't fully enlightening. :-)

The man page says that dangling commits could be "root" commits, but since my repo started as a clone of another repo, I don't see how I could have any root commits. Also, the page doesn't really describe what a dangling blob is.

So, can someone explain what these artifacts are and if they are a problem that I should be worried about?

Thanks, Larry.

Next: Shawn O. Pearce
Message 1 of 4 in “Question about fsck-objects output”
  1. Larry StreepyJan 25, 2007
  2. Shawn O. PearceJan 25, 2007
  3. Linus TorvaldsJan 25, 2007
  4. Larry StreepyJan 25, 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.