On Sat, Dec 8, 2018 at 7:45 AM Yaroslav Halchenko <yoh@xxxxxxxxxxxxxx> wrote: > I wondered, if you think it would be sensible to also add of > submodule.update which would be considered before submodule.SUBMODULE.update > variable possibly defined per submodule. That would be more inline with desire > to use any of the --merge, --rebase (and hopefully soon --reset-hard) > strategies specified as an option for submodule update, where no per-submodule > handling is happening. > > Thanks in advance for the consideration! So you are proposing a variable like submodule.update without the .<name>. that would apply to any submodule? The precedence in descending order of these configs that modify the behavior of "git submodule update" would be: * the command line flag (--merge/--rebase/--checkout) * submodule specific instructions (submodule.<name>.update) * generic submodule config (the new submodule.update) * default as --checkout I first hesitated in thinking this would be a good addition, as there is no plumbing command for submodules, to easily modify submodules irrespective of the user config. But that is out already with the submodule specific update configs. So I think it may be a good addition. I wonder if we'd be better off to re-invent the UX instead of hiding your intentions in a config setting for a command that is already long to type. What about git submodule merge git submodule rebase git submodule checkout git submodule reset (--hard) as aliases for git submodule update (...)
