From: Linus Torvalds <torvalds@osdl.org>
To: Kenneth Johansson <ken@canit.se>
Cc: git@vger.kernel.org
Subject: Re: Integrity check
Date: Tue, 6 Jun 2006 15:56:58 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606061553420.5498@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606061550100.5498@g5.osdl.org>
On Tue, 6 Jun 2006, Linus Torvalds wrote:
>
> In the future, just do "git fsck-objects --full" if you're nervous. That
> will do a full integrity check.
Btw, this can output some scary-sounding "unreachable commit xxxxxx"
messages or similar, without that actually necessarily being a problem at
all. Unreachable objects are normal if you've deleted branches, for
example, or if you rebase (or your upstream rebases, like the "pu" branch
in the git archive).
So if you just see a few unreachable objects, doing a "git prune" will get
rid of them, and they aren't normally any sign of actual trouble.
Linus
next prev parent reply other threads:[~2006-06-06 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 22:46 Integrity check Kenneth Johansson
2006-06-06 22:53 ` Linus Torvalds
2006-06-06 22:56 ` Linus Torvalds [this message]
2006-06-07 0:58 ` Dave Jones
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=Pine.LNX.4.64.0606061553420.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=ken@canit.se \
/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;
as well as URLs for NNTP newsgroup(s).