All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: "git mailing list" <git@vger.kernel.org>
Subject: Re: [RFC] repack vs re-clone
Date: Mon, 11 Feb 2008 10:45:24 -0800 (PST)	[thread overview]
Message-ID: <m3myq7e3ie.fsf@localhost.localdomain> (raw)
In-Reply-To: <e5bfff550802100025k616ccff5ib2917d283eeb0ff0@mail.gmail.com>

"Marco Costalba" <mcostalba@gmail.com> writes:

> Sometime I found myself re-cloning entirely a repository, as example
> the Linux tree, instead of repackaging my local copy.
> 
> The reason is that the published Linux repository is super compressed
> and to reach the same level of compression on my local copy I would
> need to give my laptop a long night running.

Repacking without '--force' (for gc) or '--no-reuse-delta' (low level)
would always reuse this tight packing. Only with '--force' you would
waste CPU trying to find better deltaification[*1*].
 
> So it happens to be just faster to re-clone the whole thing by upstream.

So what you are doing is passing the work, unnecessary work I'd say,
to some poor server. Not nice.


[*1*] I hope that '--no-reuse-delta' means _try_ to find better delta,
but use current one as possible delta, not stupid forget about current
deltaification at all...
-- 
Jakub Narebski
Poland
ShadeHawk on #git

  parent reply	other threads:[~2008-02-11 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  8:25 [RFC] repack vs re-clone Marco Costalba
2008-02-10 20:50 ` Nicolas Pitre
2008-02-11 18:45 ` Jakub Narebski [this message]
2008-02-11 19:20   ` Marco Costalba
2008-02-11 19:50     ` Johannes Schindelin
2008-02-11 19:51     ` Jakub Narebski
2008-02-11 20:44       ` Nicolas Pitre
2008-02-11 19:40   ` Nicolas Pitre
2008-02-11 19:53     ` Jakub Narebski

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=m3myq7e3ie.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.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.