#757297 'git status' output is confusing after 'git add -N'

Package:
git
Source:
git
Description:
fast, scalable, distributed revision control system
Submitter:
Jonathan Nieder
Date:
2014-08-07 16:39:08 UTC
Severity:
normal
#757297#5
Date:
2014-08-07 00:34:49 UTC
From:
To:
  $ git init foo
  Initialized empty Git repository in /tmp/t/foo/.git/
  $ cd foo
  $ echo hi >README
  $ git add -N README
  $ git status
  On branch master

  Initial commit

  Changes to be committed:
    (use "git rm --cached <file>..." to unstage)

          new file:   README

  Changes not staged for commit:
    (use "git add <file>..." to update what will be committed)
    (use "git checkout -- <file>..." to discard changes in working directory)

          modified:   README

If I then run "git commit", it does not actually commit the addition
of the README file.  It would be clearer to have a separate section,
like so:

  Tracked files not to be committed:
    (use "git rm --cached <file>..." to stop tracking)

           new file:   README
#757297#10
Date:
2014-08-07 01:51:14 UTC
From:
To:
ignore intent-to-add entries instead of refusing - 2012-02-07) so it
was harder to misunderstand this case.

Or make the "Changes not staged for commit" part say "new file:
README" ("modified" is implied)
#757297#15
Date:
2014-08-07 01:51:14 UTC
From:
To:
ignore intent-to-add entries instead of refusing - 2012-02-07) so it
was harder to misunderstand this case.

Or make the "Changes not staged for commit" part say "new file:
README" ("modified" is implied)
#757297#20
Date:
2014-08-07 16:31:41 UTC
From:
To:
Duy Nguyen <pclouds@gmail.com> writes:

Yeah, after reading the justification in the quoted commit, I agree
that it is status that is at fault in the above; "new file: README"
is part of "Changes not staged for commit" in this case (it is told
to the index, but the user never said it is "for commit" yet, which
is the whole point of "-N"), so instead of adding a new section, I
agree that it should be classified as "new file" not "modified"
there.
#757297#25
Date:
2014-08-07 16:31:41 UTC
From:
To:
Duy Nguyen <pclouds@gmail.com> writes:

Yeah, after reading the justification in the quoted commit, I agree
that it is status that is at fault in the above; "new file: README"
is part of "Changes not staged for commit" in this case (it is told
to the index, but the user never said it is "for commit" yet, which
is the whole point of "-N"), so instead of adding a new section, I
agree that it should be classified as "new file" not "modified"
there.