git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: Petko Manolov <petkan@nucleusys.com>
Cc: Jeff King <peff@peff.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: git and binary files
Date: Thu, 17 Jan 2008 22:52:01 -0800	[thread overview]
Message-ID: <20080118065201.GA4478@old.davidb.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0801161634080.5260@bender.nucleusys.com>

On Wed, Jan 16, 2008 at 04:39:19PM +0200, Petko Manolov wrote:

>> As an experiment, it might be worth trying to store the uncompressed
>> versions instead (git will delta _and_ compress them for you).
>
> I don't have them uncompressed.
>
> I can try to convert those files into ascii format and then save them in 
> the repository.  Since most changes are incremental git should be able to 
> generate relatively small delta, which should compress well enough.

This won't help, only make things slightly worse.

The problem is when you compress the files, as soon as there is a
difference between the two files, the output of the compressor will be
entirely different for the remainder of the file.  Unless you changes
always are at the end of the file, you will end up pretty much entire
versions in the repo.

I'm using some repos that get regular 50MB tarballs checked into them.  I
convinced them to not compress the tarballs, and git does a fairly decent
job of doing delta compression between them (although it needs quite a bit
of RAM to do so).

Dave

  parent reply	other threads:[~2008-01-18  6:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 10:34 git and binary files Petko Manolov
2008-01-16 10:54 ` David Symonds
2008-01-16 13:21   ` Petko Manolov
2008-01-16 13:42     ` Johannes Schindelin
2008-01-16 13:58       ` Petko Manolov
2008-01-16 14:07         ` Johannes Schindelin
2008-01-16 14:21           ` Petko Manolov
2008-01-16 14:34         ` Wincent Colaiuta
2008-01-16 14:45           ` Petko Manolov
2008-01-16 18:02             ` Junio C Hamano
2008-01-16 18:09               ` Junio C Hamano
2008-01-16 11:54 ` Johannes Schindelin
2008-01-16 13:39   ` Petko Manolov
2008-01-16 13:53     ` Jakub Narebski
2008-01-16 14:04       ` Petko Manolov
2008-01-16 14:20         ` Jakub Narebski
2008-01-16 14:43           ` Petko Manolov
2008-01-16 15:01             ` Nicolas Pitre
2008-01-16 15:18               ` Petko Manolov
2008-01-16 15:58                 ` Nicolas Pitre
2008-01-16 16:06                   ` Petko Manolov
2008-01-16 16:09               ` Petko Manolov
2008-01-16 16:34             ` Jakub Narebski
2008-01-16 16:41             ` Florian Weimer
2008-01-16 13:54     ` Jeff King
2008-01-16 14:14       ` Petko Manolov
2008-01-16 14:18         ` Jeff King
2008-01-16 14:25           ` Petko Manolov
2008-01-16 14:32             ` Jeff King
2008-01-16 14:39               ` Petko Manolov
2008-01-16 15:05                 ` Rogan Dawes
2008-01-18  6:52                 ` David Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-28 14:17 Jan Dittmer
2010-07-28 14:29 ` Matthieu Moy
2010-07-28 20:17   ` Avery Pennarun
2011-04-28 15:11 Git and Binary Files ryanzec
2011-04-28 15:26 ` Peter Jönsson P

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=20080118065201.GA4478@old.davidb.org \
    --to=git@davidb.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=petkan@nucleusys.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 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).