Re: git-submodule.sh respects submodule.$name.update in .git/config but not .gitmodules

On Thu, Dec 12, 2013 at 07:57:51PM +0100, Jens Lehmann wrote:

Am 12.12.2013 02:16, schrieb Junio C Hamano:

quoted

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?

Sounds good to me.  The more stuff I can leave in .gitmodules, the
happier I'll be ;).  My second step will be removing “unsafe” values
from .git/config where possible, and I'll trust myself to check
.gitmodules after pulls.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy