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

git-fsck-cache cleaning

From
Jon Loeliger <jdl@freescale.com>
Date
Aug 2, 2005, 22:24 UTC
Message-ID
<1123021481.2614.6.camel@cashmere.sps.mot.com>
Hi GITers,

So, after you dink around in a GIT tree for a while, and you discover little bloblets left around by using git-fsck-cache, what do you do? How can you clean up afterwards?

Specifically, I have a GIT tree that shows some dangling blobs that are unreferenced in my tree. Not sure how the got there, but I've verified through git-cat-file that the contents of many of those blobs are actually validly represented in my tree. Yet, fsck suggests they dangle.

So, for each of the various fsck warnings, what can be done to clean things up and yet maintain integrity in the tree? I have apparently unreferenced blobs. I should be able to just "rm .git/objects/xx/<sha1>" and be done with them, right? What about the other warnings?

Thanks, jdl

Next: Johannes Schindelin
Message 1 of 2 in “git-fsck-cache cleaning”
  1. Jon LoeligerAug 2, 2005
  2. Johannes SchindelinAug 2, 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.