git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Berkeley <patrickberkeley@gmail.com>
To: git@vger.kernel.org
Subject: Re: On Tracking Binary Files
Date: Tue, 14 Apr 2009 15:44:26 -0400	[thread overview]
Message-ID: <7efce40a0904141244n281353f3q716071d4fff5a7a0@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904141532160.6741@xanadu.home>

Thanks very much for the explanation .


On Tue, Apr 14, 2009 at 15:42, Nicolas Pitre <nico@cam.org> wrote:
> On Tue, 14 Apr 2009, Patrick Berkeley wrote:
>
>> Does Git track the deltas on binary files?
>
> Yes.  And actually git's delta storage doesn't care at all whether a
> file is text or binary.
>
>> Someone in #git mentioned that if the binaries change too much Git no
>> longer just stores the changes. If this is the case, what is the
>> breaking point where Git goes from storing the deltas to the entire
>> new file?
>
> If two versions of the same file are simply too different to make delta
> compression worth it, then no deltas are used.  It is still possible
> that a third version of the same file would produce a nice delta against
> either the first or second version though, in which case that third
> version will be stored as a delta.  And so on.
>
> A sophisticated set of euristics is applied to the list of objects as a
> whole to determine the best delta arrangement possible.  So there is no
> such thing as a simple "breaking point".
>
>
> Nicolas
>

      reply	other threads:[~2009-04-14 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7efce40a0904140741w28da9b54ucfe4b54bf48b0844@mail.gmail.com>
2009-04-14 14:42 ` On Tracking Binary Files Patrick Berkeley
2009-04-14 16:54   ` Johannes Schindelin
2009-04-14 20:05     ` Junio C Hamano
2009-04-14 20:27       ` Patrick Berkeley
2009-04-14 19:42   ` Nicolas Pitre
2009-04-14 19:44     ` Patrick Berkeley [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=7efce40a0904141244n281353f3q716071d4fff5a7a0@mail.gmail.com \
    --to=patrickberkeley@gmail.com \
    --cc=git@vger.kernel.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 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).