All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Marco Costalba <mcostalba@gmail.com>,
	git mailing list <git@vger.kernel.org>
Subject: Re: [RFC] repack vs re-clone
Date: Mon, 11 Feb 2008 20:53:34 +0100	[thread overview]
Message-ID: <200802112053.35141.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802111436100.2732@xanadu.home>

Nicolas Pitre wrote:
> On Mon, 11 Feb 2008, Jakub Narebski wrote:
> 
> > [*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...
> 
> It is really "forget about everything".  And by the time you look for 
> the best delta from scratch, remembering what was the best delta before 
> won't give you much performance gain, plus it has nasty issues like 
> making sure no delta cycles are created if you reuse an old delta, etc.

So we have either: don't try to find better delta (default), or forget
totally about old delta (--no-reuse-delta), no middle ground? That's
bad...

Or the default is try to find better delta, but reuse if better?

-- 
Jakub Narebski
Poland

      reply	other threads:[~2008-02-11 19:54 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
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 [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=200802112053.35141.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.com \
    --cc=nico@cam.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 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.