From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-fsck/lost-found's speed vs git-prune's
Date: Tue, 18 Sep 2007 11:50:49 +0200 [thread overview]
Message-ID: <20070918095049.GA9388@glandium.org> (raw)
In-Reply-To: <7v4phswcuj.fsf@gitster.siamese.dyndns.org>
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...
Mike
next prev parent reply other threads:[~2007-09-18 9:51 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 [this message]
2007-09-18 11:13 ` 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=20070918095049.GA9388@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.