Re: [PATCH 0/2] Add an update=none option for 'loose' submodules
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 11, 2011, 18:28 UTC
- Message-ID
- <7v8vqzreeo.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <cover.1312923673.git.hvoigt@hvoigt.net>
Heiko Voigt <hvoigt@hvoigt.net> writes:
> If a submodule is used to seperate some bigger parts of a project into > an optional directory it is helpful to not clone/update them by default.
Sorry if I am slow, but I do not get this.
I thought unless you say "submodule init" once, a submodule you are not interested in should not be cloned nor updated at all. If that is not the case, isn't it a bug to be fixed without a new configuration variable that fixes it only when it is set?
> We have been talking about loose submodules for some time:
Also before introducing a new terminology "loose submodule", please define it somewhere. It feels confusing to me that a normal submodule, which shouldn't be auto-cloned nor auto-updated without "submodule init", needs to be called by a name other than simply a "submodule" but with an adjuctive "loose submodule".