From: Raymond Jennings <shentino@gmail.com>
To: git@vger.kernel.org
Subject: Bug in default commit hook (improperly forbidding a single blank line at EOF)
Date: Mon, 7 Sep 2015 18:37:29 -0700 [thread overview]
Message-ID: <55EE3BD9.7020707@gmail.com> (raw)
Please see https://bugs.gentoo.org/show_bug.cgi?id=559920 for further
details.
Files *should* have a single blank line at the end, because a line
should always have a newline at the end.
Adding a newline to the end of a file whose last line doesn't have one
should be legal...as long as you don't create empty lines at the end.
next reply other threads:[~2015-09-08 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 1:37 Raymond Jennings [this message]
2015-09-08 4:55 ` Bug in default commit hook (improperly forbidding a single blank line at EOF) Jeff King
2015-09-08 5:03 ` Raymond Jennings
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=55EE3BD9.7020707@gmail.com \
--to=shentino@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.