Linus Torvalds wrote:
quoted text
> > Does this consider the case where the intent of the subprojects are to
> > collate multiple, small projects into one bigger project?
> > 
> > In that case, you might want to keep all of the subprojects in the same
> > git repository.
>
> I assume you mean "you might want to keep all of the subprojects' objects 
> in the same git object directory".
>
> And yes, that's absolutely true, but it's technically no different from 
> just using GIT_OBJECT_DIRECTORY to share objects between totally unrelated 
> projects, or using git/alternates to share objects between (probably 
> *less* unrelated repositories, but still clearly individual repos).
>   

Would that be the only distinction?

Would submodules be descended into for object reachability questions?

quoted text
> So the main point of superproject/subprojects is to allow independence 
> (because independence is what allows it to scale), but there is nothing to 
> say that things *have* to kept totally isolated. 
>   

I'm particularly interested in repositories with, say, thousands of
submodules but only a few hundred meg. I really want to avoid the
situation where each of those submodules gets checked or descended into
separately for updates etc.

Sam.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html