VMiklos, Sun, Jul 15, 2007 12:54:50 +0200: > Na Sun, Jul 15, 2007 at 12:47:12PM +0200, Alex Riesen <raa.lkml@xxxxxxxxx> pisal(a): > > to. Subprojects defined in such a loosely way are more flexible then > > having git-pull fetch subprojects by default. Sometimes I even want be > > _sure_ the subprojects are completely untouched (I have some critical > > parts in them). > > Okay, but where can you overwrite that default? It would be nice to have > a config variable for this or something like that. It is not a default in a sense where it control the behaviour of a git command. git pull just does not do anything to subprojects and you use a separate command (git-submodule update, I believe) to update them. That said, I never used the git-submodule, nor did I have an urge to. As I said, I find it convenient enough as it is with git-add and git-diff, checking out the subproject as needed. Have to be careful about "git commit -a" (which I almost never use anyway) and haven't had conflicts yet. - 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
