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

git diff --check always shows line 1 for blank at EOF for new files

From
Christoph Mallon <christoph.mallon@gmx.de>
Date
Oct 6, 2010, 09:27 UTC
Message-ID
<4CAC411E.3010204@gmx.de>
Hi,

there seems to be a glitch in git diff --check for new files: If a new file has trailing empty lines, then the error message always refers to line 1. This happens with git 1.7.3.1.

Here is a simple test case:
   git init test
   cd test
   printf 'a\nb\nc\n\n' > file
   git add -AN
   git diff --check
The last command will show "file:1: new blank line at EOF.".
It works fine, if the diff is not against /dev/null, e.g.:
   git init test
   cd test
   printf 'a\nb\nc\n' > file
   git add -A
   echo >> file
   git diff --check
This correctly shows "file:4: new blank line at EOF.".
Next: Jonathan Nieder
Message 1 of 4 in “git diff --check always shows line 1 for blank at EOF for new files”
  1. Christoph MallonOct 6, 2010
  2. Jonathan NiederOct 7, 2010
  3. Christoph MallonOct 7, 2010
  4. Junio C HamanoOct 10, 2010

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.