Re: Managing submodules on large multi-user projects

[Avery Pennarun <apenwarr@gmail.com>]

On Fri, May 29, 2009 at 2:41 PM, R. Tyler Ballance <tyler@slide.com> wrote:
> As some of you may recall from my last swath of emails to the list
> regarding memory usage and repository size, we have quite a large
> repository. About a month ago, I added a submodule to the primary repo
> in an effort to start to segment where possible, particularly around
> third party modules.
>
> I've noticed that keeping submodules updated is an absolute pain,
> particularly with a large multiuser setup with *lots* of branches.

Just so I understand, is the reason you're splitting into submodules
*just* to avoid memory usage / repository size issues?  I can sort of
understand the memory usage issues - sort of - but how does it reduce
repository size if you need to need to check out all the submodule
repositories along with the main project anyway?

Just looking to clarify for myself.  (I'm continuing my work on
git-subtree, which is getting more and more positive feedback.  It
solves all the *other* problems that you listed vs. submodules, but it
certainly doesn't resolve any repository size issues.)

Have fun,

Avery