From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: git@vger.kernel.org
Subject: Problems with large compressed binaries when converting from svn
Date: Tue, 6 Jan 2009 13:55:12 +0100 [thread overview]
Message-ID: <c09652430901060455l5179888ep3c51ff4e3dd5a6ef@mail.gmail.com> (raw)
I'm converting from svn and I've run into a
problem with tar.gz and tar.bz2 compressed files.
(This is a separate but only slightly related to previous post).
In subversion we committed large tar.bz2/gz files. These files would
change relatively rarely, but only very slightly. The trouble with the tar.bz2
format is that if the first byte changes, then the rest of the file will also
be different. .zip does not have this problem, but .zip isn't a very friendly
format for our purposes.
Later on the tar.bz2/gz files started to change fairly often, but harddrives
get bigger much more quickly than the .svn repository grows so we just
kept doing things the same way rather than reeducate and reengineer
the procedures.
With .git we need to handle this differently somehow.
Does git have some capability to store diffs of compressed files efficiently?
The only other alternative I can think of is to commit uncompressed
.tar files which is a bit of a bump in the road, but I suppose could be
made to work.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
next reply other threads:[~2009-01-06 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 12:55 Øyvind Harboe [this message]
2009-01-07 23:55 ` Problems with large compressed binaries when converting from svn Alex Riesen
2009-01-08 7:33 ` Øyvind Harboe
2009-01-08 10:01 ` Johan Herland
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=c09652430901060455l5179888ep3c51ff4e3dd5a6ef@mail.gmail.com \
--to=oyvind.harboe@zylin.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).