* core.whitespace blank-at-eof on by default?
@ 2010-04-23 14:58 Dan Savilonis
0 siblings, 0 replies; only message in thread
From: Dan Savilonis @ 2010-04-23 14:58 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-04-23 14:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-23 14:58 core.whitespace blank-at-eof on by default? Dan Savilonis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).