From: Junio C Hamano <junkio@cox.net>
To: Ming Lei <mlei@brocade.com>
Cc: git@vger.kernel.org
Subject: Re: fsck-object --standalone got errors
Date: Wed, 08 Mar 2006 19:17:18 -0800 [thread overview]
Message-ID: <7v7j74fgsh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <440F945C.2010401@brocade.com> (Ming Lei's message of "Wed, 08 Mar 2006 18:35:08 -0800")
Ming Lei <mlei@brocade.com> writes:
> I have a repository created by GIT itself(not cognito, etc). It has
> branches called base, master and origin. When I did git-fsck-objects
> --full there is nothing shown, but when I did git-fsck-objects
> --standalone, it displayed following:
That is really an artifact from a distant past. Please do not
worry about that error -- as long as --full does not see
anything long, there is nothing wrong with your repository.
The fsck-object command (back then it was called fsck-cache)
complained if objects referred to by files in .git/refs/ or
objects stored in files under .git/objects/??/ are not found as
stand-alone SHA1 files (i.e. found in alternate object pools or
packed archives stored under .git/objects/pack). Back then,
packs and alternates were curiosity and having everything as
loose objects were the norm.
When we adjusted the behaviour of fsck-cache to consider objects
found in packs are OK, we introduced the --standalone flag as a
backward compatibility measure.
It still correctly checks if your repository is complete and
consists only of loose objects, so in that sense it is doing the
"right" thing, but checking that is pointless these days. We
probably should remove that flag.
next prev parent reply other threads:[~2006-03-09 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 2:35 fsck-object --standalone got errors Ming Lei
2006-03-09 3:17 ` Junio C Hamano [this message]
2006-03-09 10:37 ` [PATCH] fsck-objects: Remove --standalone Junio C Hamano
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=7v7j74fgsh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mlei@brocade.com \
/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