git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-fsck/lost-found's speed vs git-prune's

From
Mike Hommey <mh@glandium.org>
Date
Sep 18, 2007, 09:50 UTC
Message-ID
<20070918095049.GA9388@glandium.org>
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:
Show 7 quoted lines
> 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
Previous: Junio C HamanoNext: Johannes Schindelin
Message 4 of 5 in “git-fsck/lost-found's speed vs git-prune's”
  1. Mike HommeySep 18, 2007
  2. Sam VilainSep 18, 2007
  3. Junio C HamanoSep 18, 2007
  4. Mike HommeySep 18, 2007
  5. Johannes SchindelinSep 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.