Am 12.12.2013 02:16, schrieb Junio C Hamano: > "W. Trevor King" <wking@xxxxxxxxxx> writes: > >> For >> safety, maybe the default `init` should copy *everything* into >> .git/config, after which users can remove stuff they'd like to >> delegate to .gitmodules. > > Copying everything into config is "be unsafe and inconvenient by > default for everybody", isn't it? Folks who want safety are forced > to inspect the resulting entries in their config file (which is more > inconvenent if you compare with the design where nothing is copied > and nothing dynamically defaults to what then-current .gitmodules > happens to contain). Folks who trust those who update .gitmodules > for them are forced to update their config every time upstream > decides to use different settings in .gitmodules, because they have > stale values in their config that mask what are in .gitmodules. > > I think the solution we want is to copy only minimum to the config > (and that "minimum" may turn out to be "nothing"), and to default > keys that are only absolutely safe to .gitmodules file. I agree and will prepare a patch for that. What about teaching "git submodule sync" the "--url", "--update", "--fetch", "--ignore", "--branch" and "--all" options to allow the user to copy the current settings he wants from .gitmodules to .git/config (but only safe values of course)? Trevor, would you be ok to issue another command to copy everything to .git/config? -- 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