A Large Angry SCM <gitzilla@xxxxxxxxx> writes: > Junio C Hamano wrote: >> Andrew insists --whitespace=warn should be the default, and I >> tend to agree. This introduces --whitespace=warn, so if your >> project policy is more lenient, you can squelch them by having >> apply.whitespace=nowarn in your configuration file. >> Signed-off-by: Junio C Hamano <junkio@xxxxxxx> > > I think this is wrong. The default policy of, non-security, tools > SHOULD be the least restrictive and most flexible. The reason is that --whitespace=warn does not refuse to apply but spits out some warning messages. Admittedly, going from zero, any amount of new warning message makes it infinitely more chatty, but then people can squelch it by having the configuration option "apply.whitespace = nowarn". - : 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