On Sun, May 20, 2007 at 11:24:32PM +0200, Alex Riesen wrote: > Sven Verdoolaege, Sun, May 20, 2007 23:09:54 +0200: > > On Sun, May 20, 2007 at 10:54:44PM +0200, Alex Riesen wrote: > > > Sven Verdoolaege, Sun, May 20, 2007 21:59:30 +0200: > > > > > I am very worried about this big red switch that says "all > > > > > subprojects to be cloned and checked out, or nothing". I think > > > > > this would not work well with projects that truly need > > > > > superproject support (i.e. very large ones, where most people > > > > > would not want to clone and check out every single subproject). > > > > > > > > It's pretty easy to add a "submodule.*.skip" or "submodule.*.ignore". > > > > Since the subcloning only happens at checkout, you could set these > > > > before doing a checkout. > > > > > > And set them back after doing the checkout? > > > > What do you mean? Why would you set them back? > > Why should I set them before doing a checkout? > > > I guess I'm missing something. > > "checkout" is an operation which is done often. It never had to be > configured before. There is going to have to be *some* way of selecting which subprojects you want to check out. A config option that you have to set only once (or not at all if you are happy with the default) seems to be the easiest way. You can have git-gui set them for you if you want. How would _you_ specify which subprojects to checkout ? > > Well... the subproject as a whole is independent of the superproject, > > but the checkout in the superproject is not entirely independent. > > > > Junio was talking about branch in subproject, wasn't he? That's a local thing. skimo - 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
