Theodore Tso <tytso@xxxxxxx> writes: > Coding-style only changes tends to screw up our ability to merge > pending patches, but I'll take care of it, thanks. Exactly. And looking at the patch the old code was already perfectly readable anyways. Benefit about zero. I also don't see how you can take care of patch conflicts caused by this for patches not yet in your tree but still in development somewhere else. IMHO any coding style cleanup should only done on code that changes anyways, but not on other code. The recent flurry of cleanup code patches on l-k causes far more problems than it solves. I'm not even sure why people do this? Just because it is en vogue recently? If they want to contribute in simple ways to the Linux kernel I'm sure actually really useful things can be found that they can change. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
