git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: thin packs ending up fat
Date: Fri, 13 Jan 2012 10:15:45 -0500	[thread overview]
Message-ID: <20120113151545.GA9373@sigill.intra.peff.net> (raw)
In-Reply-To: <7vmx9sysqe.fsf@alter.siamese.dyndns.org>

On Thu, Jan 12, 2012 at 11:19:37PM -0800, Junio C Hamano wrote:

> I wanted to make sure I understood the root cause of the issue and the
> approach the patch takes to address it, instead of committing something
> that smelled correct. And the only way I know to do so is to write it
> down.

I use something of the same technique myself...

> Especiallly, before coming up with the description, I was wondering if
> this kind of symptom appears in non-thin cases, but after writing down the
> justification for this patch, it became clear that we wouldn't have to
> worry too much about that case. In a non-thin pack, we need to record one
> object at least in a delta family in inflated base form, so we may as well
> send that one near the tip that is already in that form for that, letting
> the existing "avoid futile delta" heuristics to kick in. Other objects in
> the same delta family will delta against it.

Exactly. You asked earlier why my one-liner patch was not in the first
message. It's because it was only through writing the first message that
I came to the same realization. :)

-Peff

  reply	other threads:[~2012-01-13 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 22:15 thin packs ending up fat Jeff King
2012-01-12 22:32 ` Jeff King
2012-01-12 23:54   ` Nicolas Pitre
2012-01-13  0:14   ` Junio C Hamano
2012-01-13  1:31   ` Junio C Hamano
2012-01-13  1:51     ` Jeff King
2012-01-13  1:59       ` Jeff King
2012-01-13  7:19       ` Junio C Hamano
2012-01-13 15:15         ` Jeff King [this message]
2012-01-13  2:19     ` Nicolas Pitre
2012-01-13  8:28 ` Ævar Arnfjörð Bjarmason
2012-01-13 15:55   ` Jeff King

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=20120113151545.GA9373@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nico@fluxnic.net \
    /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).