On Wed, 12 Dec 2018, Stefan Beller wrote:
> > But again, I must confess, that either I forgot or just do not see a
> > clear use-case/demand for submodule.update config myself any longer,
> ok, let's drop that patch then.
ok, But I will cherish it in my memory so whenever the use case
comes ba
> But again, I must confess, that either I forgot or just do not see a
> clear use-case/demand for submodule.update config myself any longer,
ok, let's drop that patch then.
> Probably I need to try "submodules update --merge" to see what is that
> rough edge which makes it different from the pot
On Mon, 10 Dec 2018, Stefan Beller wrote:
> Signed-off-by: Stefan Beller
> ---
> > > So you are proposing a variable like submodule.update
> > [...]
> > Glad to hear that. Not sure though I would know where to stick my
> > nose to figure out what to change. ;-)
> The update_module is compute
Signed-off-by: Stefan Beller
---
> > So you are proposing a variable like submodule.update
> [...]
>
> Glad to hear that. Not sure though I would know where to stick my
> nose to figure out what to change. ;-)
The update_module is computed via the submodule--helpers
update-module-mode command, w
4 matches
Mail list logo