{"thread":{"id":"23580","subject":"core.whitespace blank-at-eof on by default?","startedAt":"2010-04-23T14:58:48Z","lastAt":"2010-04-23T14:58:48Z","messageCount":1,"participants":["Dan Savilonis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"140219","messageId":"u2k325c62f61004230758xc5dbd87dza2515fac8e2e505b@mail.gmail.com","threadId":"23580","inReplyTo":null,"subject":"core.whitespace blank-at-eof on by default?","fromName":"Dan Savilonis","fromEmail":"djs@n-cube.org","sentAt":"2010-04-23T14:58:48Z","receivedAt":"2010-04-23T14:58:48Z","isPatch":false,"sender":{"key":"djs@n-cube.org","avatar":null},"body":"I noticed the blank-at-eof whitespace error is on by default after\n77b15bb. As a result, correcting a C file with no blank line at EOF is\nmarked as a whitespace error, even though the C standard requires\nthis.\n\nWhat is the intent of this rule? To prevent extra blank lines at EOF,\nor any at all? Would it make more sense to only warn only one the\naddition of 2+ blank lines or when a blank line is already present at\nEOF?\n\nDan\n"}]}