From: Rogan Dawes <lists@dawes.za.net>
To: Petko Manolov <petkan@nucleusys.com>
Cc: Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git and binary files
Date: Wed, 16 Jan 2008 17:05:57 +0200 [thread overview]
Message-ID: <478E1D55.3050108@dawes.za.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0801161634080.5260@bender.nucleusys.com>
Petko Manolov wrote:
> On Wed, 16 Jan 2008, Jeff King wrote:
>
>> OK, that was the answer I was looking for; it looks like you are out
>> of luck.
>
> Story of my life. :-)
>
>> 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.
>
> Thanks for the hint.
>
>
> Petko
That is unlikely to help, since git can find deltas in binary files just
as easily as in text files. All you are doing is changing the encoding.
Rogan
next prev parent reply other threads:[~2008-01-16 15:09 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 [this message]
2008-01-18 6:52 ` David Brown
-- 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=478E1D55.3050108@dawes.za.net \
--to=lists@dawes.za.net \
--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 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.