[PATCH 0/2] Add an update=none option for 'loose' submodules

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.

This series implements a new value 'none' for submodule.<name>.update. If this option is set a submodule will not be updated or cloned by default. If the user wants to work with the submodule he either needs to explicitely configure the update option to 'checkout' or pass --checkout as an option to the submodules. I chose this name to be consistent with the existing --merge/--rebase options.

We have been talking about loose submodules for some time:

RFC patch for this series http://thread.gmane.org/gmane.comp.version-control.git/175165

Using submodule groups/dependencies: http://thread.gmane.org/gmane.comp.version-control.git/130928/focus=131050 http://thread.gmane.org/gmane.comp.version-control.git/176347/focus=178614

This lays the foundations for grouping of submodules. Once submodule grouping will be implemented the value of submodule.$name.update provides the default value when the user specifies no group. A group specification could then be a layer on top which provides a shortcut to choose other submodule.$name.update values to be registered in .git/config.

Heiko Voigt (2):
  submodule: move update configuration variable further up
  add update 'none' flag to disable update of submodule by default

 Documentation/git-submodule.txt |    8 ++++-
 git-submodule.sh                |   22 ++++++++++----
 t/t7406-submodule-update.sh     |   62 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 85 insertions(+), 7 deletions(-)