* Problem using 'submodule.recurse'
@ 2019-05-23 17:42 Maksim Odnoletkov
0 siblings, 0 replies; only message in thread
From: Maksim Odnoletkov @ 2019-05-23 17:42 UTC (permalink / raw)
I have a problem using 'submodule.recurse' config option. I want to use
it and at the same time fine-tune behavior for individual commands with
more specific options. For example to keep 'on-demand' behavior for
'fetch' and 'pull'.
* If I put 'fetch.recurseSubmodules = on-demand' *below*
'submodule.recurse = true' in the config, it kinda works - fetch will
use 'on-demand' behavior.
* But with this setup 'fetch' within 'pull' will always recurse
unconditionally. Looking at the code this happens because 'pull'
reads 'submodule.recurse' and seeing it in non-default state forces
this behavior on underlying 'fetch'.
As far as I understand there is no way currently to have 'on-demand'
recursing for 'fetch' within the 'pull' when 'submodule.recurse' is on
(outside of using command line args). Also with described setup 'fetch'
behaves differently from 'pull' which is unexpected.
Looking at the code quickly I see two ways this can be resolved:
* Add 'pull.recurseSubmodules' option so it can be used to explicitly
override 'submodule.recurse' for 'pull'.
* Don't force recursing behavior from 'pull' to underlying 'fetch' if
it comes from config and not from command line args.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-05-23 17:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-23 17:42 Problem using 'submodule.recurse' Maksim Odnoletkov
Code repositories for project(s) associated with this inbox:
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 read-only IMAP folder(s) and NNTP newsgroup(s).