From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git-fsck/lost-found's speed vs git-prune's
Date: Tue, 18 Sep 2007 12:13:14 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709181211560.28586@racer.site> (raw)
In-Reply-To: <20070918095049.GA9388@glandium.org>
Hi,
On Tue, 18 Sep 2007, Mike Hommey wrote:
> On Tue, Sep 18, 2007 at 02:18:44AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> > Mike Hommey <mh@glandium.org> writes:
> >
> > > I was wondering if that was to be expected for git-fsck to be
> > > significantly slower than git-prune (by several orders of magnitude) ?
> >
> > fsck validates objects are correct and sane. prune only looks
> > at reachability.
>
> Now, the speed difference makes sense, but I wouldn't expect lost-found
> to actually bother validating objects...
That's why we should get rid of lost-found, and only keep the --lost-found
option to git-fsck, to make it clear.
And I think that it is too rare that you lost objects and want to find
them, to warrant a fast version of it.
Ciao,
Dscho
prev parent reply other threads:[~2007-09-18 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 9:09 git-fsck/lost-found's speed vs git-prune's Mike Hommey
2007-09-18 9:14 ` Sam Vilain
2007-09-18 9:18 ` Junio C Hamano
2007-09-18 9:50 ` Mike Hommey
2007-09-18 11:13 ` Johannes Schindelin [this message]
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.0709181211560.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mh@glandium.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;
as well as URLs for NNTP newsgroup(s).