I noticed the blank-at-eof whitespace error is on by default after 77b15bb. As a result, correcting a C file with no blank line at EOF is marked as a whitespace error, even though the C standard requires this. What is the intent of this rule? To prevent extra blank lines at EOF, or any at all? Would it make more sense to only warn only one the addition of 2+ blank lines or when a blank line is already present at EOF? Dan -- 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