Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > On Thu, Dec 10, 2020 at 12:28 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > ... >> how much damage are we causing to >> existing users who expect the command to work the way it currently >> does? > > Zero. Because my proposal does *not* make the pull fail, it merely > prints a warning that it will change in the future. The approach to hold the "future" patch of and keep giving a "warning" is still likely to cause damage to people like Ted and Dscho (both gave examples of workflowsand automation that currently happily creating merges as the user expects, while the user just ignores the warning, without being configured at all), when finally the "future" patch (after fixing the test breakages, of course) lands. They just ignored the current loud messages---I do not see any reason to expect the updated "warning" would have any effect on them and help them to prepare for the future default change. It is either being dishonest or deliberatly closing eyes to say "Zero" after hearing what they said, I would have to say.
