From: Nicolas Pitre <nico@cam.org>
To: David Brown <git@davidb.org>
Cc: Git <git@vger.kernel.org>
Subject: Re: Removing old data without disturbing tree?
Date: Tue, 27 Nov 2007 15:06:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.99999.0711271459520.9605@xanadu.home> (raw)
In-Reply-To: <20071127193955.GA16585@old.davidb.org>
On Tue, 27 Nov 2007, David Brown wrote:
> An upstream tree I'm mirroring with git-p4 has decided to start checking
> in large tarballs (150MB) periodically. It's basically a prebuild version
> of some firmware needed to run the rest of the software.
>
> Git doesn't seem to have any problem with these tarballs (and is using a
> lot less space than P4), but I have a feeling we might start running into
> problems when things get real big. Does anyone have experience with packs
> growing beyong several GB?
It should just work. It was tested with artificial data sets but that's
about it.
Now if those tarballs are actually multiple revisions of the same
package, you might consider storing them uncompressed and let Git delta
compress them against each other which will produce an even more
significant space saving.
Nicolas
next prev parent reply other threads:[~2007-11-27 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:39 Removing old data without disturbing tree? David Brown
2007-11-27 20:06 ` Nicolas Pitre [this message]
2007-11-27 21:10 ` David Brown
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=alpine.LFD.0.99999.0711271459520.9605@xanadu.home \
--to=nico@cam.org \
--cc=git@davidb.org \
--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).