git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bug in default commit hook (improperly forbidding a single blank line at EOF)

From
RJRaymond Jennings <shentino@gmail.com>
Date
Sep 8, 2015, 01:37 UTC
Message-ID
<55EE3BD9.7020707@gmail.com>

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: Jeff King
Message 1 of 3 in “Bug in default commit hook (improperly forbidding a single blank line at EOF)”
  1. Raymond JenningsSep 8, 2015
  2. Jeff KingSep 8, 2015
  3. Raymond JenningsSep 8, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.