* Wilson, Kevin Lee (OpenView Engineer) <kevin.l.wilson@xxxxxx> 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@xxxxxxxx mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html