From: Jonathan Nieder <jrnieder@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
"W. Trevor King" <wking@tremily.us>,
Heiko Voigt <hvoigt@hvoigt.net>,
Charlie Dyson <charlie@charliedyson.net>,
git@vger.kernel.org
Subject: Re: git-submodule.sh respects submodule.$name.update in .git/config but not .gitmodules
Date: Thu, 12 Dec 2013 11:23:01 -0800 [thread overview]
Message-ID: <20131212192301.GQ2311@google.com> (raw)
In-Reply-To: <52AA072F.2000105@web.de>
Jens Lehmann wrote:
> Am 12.12.2013 02:16, schrieb Junio C Hamano:
>> 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)?
Why would I want to copy settings to .git/config when they are safe
enough to already be used directly from .gitmodules and the value from
.gitmodules is the one chosen to make sense when working with the
current revision?
URLs are kind of special because generally the newest value is the
most meaningful one, even when looking back over old history.
Thanks,
Jonathan
next prev parent reply other threads:[~2013-12-12 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 15:48 git-submodule.sh respects submodule.$name.update in .git/config but not .gitmodules Charlie Dyson
2013-12-09 22:35 ` Heiko Voigt
2013-12-09 23:40 ` Junio C Hamano
2013-12-11 22:26 ` Jens Lehmann
2013-12-11 22:44 ` W. Trevor King
2013-12-12 1:16 ` Junio C Hamano
2013-12-12 18:57 ` Jens Lehmann
2013-12-12 19:14 ` W. Trevor King
2013-12-12 19:23 ` Jonathan Nieder [this message]
2013-12-12 21:17 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131212192301.GQ2311@google.com \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=charlie@charliedyson.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=wking@tremily.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).