John Feuerstein <john@xxxxxxxxxx> writes: > I had to rewrite history recently (ugh -- private repo, not shared with > anybody) and wanted to change the commit message of the root commit. > During this I've encountered a failing git-rebase if apply.whitespace is > set to "error". > > Should whitespace-errors really be detected when rebasing? > (or worse: be "fixed" without explicitely asking for it when using a > global apply.whitespace=fix setting) I've seen this argued both ways. Some people seem to be happy that they can use rebase with whitespace=fix to clean up their mess. Some people quite rightly oppose it (I am slightly closer to the latter camp myself, but that does not count that much). I'd agree that whitespace=error won't help anybody here. Perhaps rebase can be taught to take --whitespace=warn from the command line to override whatever is in the configuration? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html