"Eckhard Maaß" <eckhard.s.maass@xxxxxxxxxxxxxx>: > On Tue, May 01, 2018 at 01:09:06PM +0200, Matthieu Moy wrote: > > That init_diff_ui_defaults() should indeed have been before > > git_config() from the beginning. My bad, I'm the one who > > misplaced it apparently :-(. > Should I have done this "bug fix" in a separate commit or mention it in > the commit message? I'm fine with it as-is. Before your "fix", the config was ignored because overwritten by init_diff_ui_defaults() after reading the config, so effect of your change is indeed what the commit message describes. I'm often thinking aloud while reviewing, don't take my comments as objections. > > This "break_opt = 0" deserves a mention in the commit message IMHO. > > I'm not 100% sure it's a good change actually. > Hm, what problems do you see here? I don't see any "problem", I *think* your change is good, but I can't fully convince myself that it is without further explanation. Unlike the other two, this option has no corresponding configuration variable, so the "let the config" argument doesn't apply. For "git status", there's actually not even a command-line option. So, this assignment removed, there's no way in the user-interface to re-enable the previous behavior. *If* there was a good reason to get "break_opt = 0", then your patch is breaking it. Unfortunately, the commit introducing it doesn't help much: f714fb8 (Enable rewrite as well as rename detection in git-status, 2007-12-02) is just a one-liner message with a one-liner patch. But actually, I never used -B/--break-rewrites, and writting this message I tried to get a case where -B would make a difference and I'm not even able to find one. So, as someone who never understood the real point of -B, I'm not sure I'm qualified to juge on what's the best default ;-). -- Matthieu Moy https://matthieu-moy.fr/
