From: Enrico Weigelt <weigelt@metux.de>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GIT as binary repository
Date: Thu, 21 Oct 2010 21:19:25 +0200 [thread overview]
Message-ID: <20101021191925.GE28700@nibiru.local> (raw)
In-Reply-To: <2EBB46ACFCD6CF48B45E2B1865BD02338037D36B4E@GVW1098EXB.americas.hpqcorp.net>
* Wilson, Kevin Lee (OpenView Engineer) <kevin.l.wilson@hp.com> wrote:
Hi,
> We are investigating the use of GIT as a binary repository solution.
> Our larger files are near 800MB and the total checked out repo size
> is about 3 GB the repo size in SVN is more like 20-30GB, if we could
> prune the history prior to MR, we could get these sizes down
> considerably. This binary repo is really for our super project build.
What exactly do you need such large binary objects in an git repo ?
IMHO, Git isn't made for large files. I've noticed this when doing
git-based mail archives on an old P3 box w/ 256MB physical memory.
I had to split mbox'es to maildirs.
Perhaps you would like to have a look at some pure object store like
venti ? (It's not distributed yet, but I'm currently working on an
distributed successor, called Nebulon, which will also support
strong encryption, on-demand replication, etc).
> I also have some questions, about how the workflow would be for
> getting all of the changes merged from several different teams
> into the one repository would operate.
IMHO, there should be some dedicated release manager role, which
is responsible for merging finished branches into the mainline
(eg. similar that Linus does for the official Linux tree).
BUT: you perhaps should think carefully, whether you need everything
in one big repo. Perhaps a bunch of smaller ones (eg. having separate
modules in the own repos/trees) would fit better.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
prev parent reply other threads:[~2010-10-21 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:52 GIT as binary repository Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 14:19 ` Tay Ray Chuan
2010-10-21 19:54 ` Enrico Weigelt
2010-10-21 21:23 ` Shawn Pearce
2010-10-22 5:02 ` Enrico Weigelt
2010-10-22 19:20 ` Shawn Pearce
2010-10-21 17:38 ` Shawn Pearce
2010-10-21 18:53 ` Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 19:19 ` Enrico Weigelt [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=20101021191925.GE28700@nibiru.local \
--to=weigelt@metux.de \
--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).