On Thu, Jun 05, 2014 at 11:18:28AM -0700, Junio C Hamano wrote: > Jens Lehmann <jens.lehm...@web.de> writes: > > We had two settings in mind,... > > So what if clone would just do an "git submodule init" for now when > > "submodule.autoinit" is set but "submodule.autoupdate" isn't [?] > > ... and a single "submodule.auto" setting would be what users really want? > > I do not offhand think of a sensible scenario where you want to init > a submodule once but do not want to update it when the superproject > changes. Even if the user uses the mode to detach the submodule > HEAD, i.e. the branches in submodules do not matter and the whole > tree is described by the superproject's commit and gitlinks recorded > in it, the user would want the new objects necessary for the updated > superproject, which means a submodule that is init'ed (whether it is > via "git submodule init" or the submodule.autoinit variable) must be > updated.
I agreed that once we have the ability to do so, autoupdating any initialized submodules should be automatic and non-optional. However, making it optional during a transition period while the ability gets fleshed out would make sense too (so checkout-mode folks can opt in before we clobber the local-branch folks ;). Ceers, 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
signature.asc
Description: OpenPGP digital signature
