On Thu, 24 May 2007, Sven Verdoolaege wrote: > > If you allow an override, then I don't see how having the initial > information in the tree is any better. > When new information gets in from the tree, you're going to ignore it anyway. Well, duh. "Paging Mr Ovious". IF you have local overrides they get ignored. Which is what _should_ happen, of course. > What if someone is working on his own branch of the superproject > that needs some changes in his own subproject? > He needs to modify .gitmodules, but when the changes go upstream, > this .gitmodules changes get merged as well. > Now imagine several developers doing this. > You end up continually having to modify .gitmodules. Ehh. What drugs are you on? That's the whole point of having local overrides. You use them for local branches. You do _not_ use .gitmodules for those. So ".gitmodules" is the default for people who don't do anything special. Only people who change the _default_ would ever change that. I really don't understand or see your objections at all. You are making totally idiotic arguments BASED ON DOING OBVIOUSLY STUPID THINGS. That's not an argument. Linus - 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
