Git development
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Git List <git@vger.kernel.org>
Subject: git-fsck-cache cleaning
Date: Tue, 02 Aug 2005 17:24:41 -0500	[thread overview]
Message-ID: <1123021481.2614.6.camel@cashmere.sps.mot.com> (raw)

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

             reply	other threads:[~2005-08-02 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 22:24 Jon Loeliger [this message]
2005-08-02 23:06 ` git-fsck-cache cleaning Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1123021481.2614.6.camel@cashmere.sps.mot.com \
    --to=jdl@freescale.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox