From: Dan Savilonis <djs@n-cube.org>
To: git@vger.kernel.org
Subject: core.whitespace blank-at-eof on by default?
Date: Fri, 23 Apr 2010 10:58:48 -0400 [thread overview]
Message-ID: <u2k325c62f61004230758xc5dbd87dza2515fac8e2e505b@mail.gmail.com> (raw)
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
reply other threads:[~2010-04-23 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u2k325c62f61004230758xc5dbd87dza2515fac8e2e505b@mail.gmail.com \
--to=djs@n-cube.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).