Hi Dscho,
Le 2021-09-10 à 06:46, Johannes Schindelin a écrit :
Hi Philippe,
On Thu, 9 Sep 2021, Philippe Blain wrote:
Le 2021-09-09 à 06:53, Johannes Schindelin a écrit :
On Wed, 8 Sep 2021, Philippe Blain wrote:
Anyway, I'm not saying that we should not do what this patch is
proposing, but I think caveats such as that should be documented in the
commit message, and maybe an audit of other configs that might results
in behavioural differences should be done.
Since this is already a bug in the `apply` backend, it would be even
better to follow-up with a fix, hint, hint, nudge, nudge ;-)
I'm not sure I understand what you are saying. The fact that 'rebase'
does not pay attention to 'submodule.recurse' is not a bug in my opinion,
it's just a limitation of the current code... Or do you mean something else?
I must have misunderstood you. I thought you were saying that Phillip's
patch introduces the regression where `submodule.recurse` is no longer
respected.
Ciao,
Dscho
Well it does, but only for the initial checkout of 'onto'. But as I wrote in
[1], I think that half respecting 'submodule.recurse' is confusing UX. So
I would think that it is not *that* bad to keep Phillip's patch as-is in the meantime
i.e. while we wait for 'git rebase --recurse-submodules' to materialize. I think
that it would not be good UI either to have rebase respect 'submodule.recurse',
but not having a --recurse-submodules flag like all other commands that honor
that config.
Thanks,
Philippe.
P.S. I did not CC you in [1], should I have? What's the etiquette around this,
i.e. should I manually add CC's for people involved in "parallel" threads in
addition to everyone I get by doing "reply-all" ?
1. https://lore.kernel.org/git/pull.1034.git.1631108472.gitgitgadget@xxxxxxxxx/T/#m182b8d5f24b41c2ff8e919819229974d71258cd9
