On Thu, Aug 7, 2014 at 7:34 AM, Jonathan Nieder <[email protected]> wrote:
> Package: git
> Version: 1:2.0.0-1
> Tags: upstream
>
> $ 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.
We used to reject such a commit operation before 3f6d56d (commit:
ignore intent-to-add entries instead of refusing - 2012-02-07) so it
was harder to misunderstand this case.
> 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
>
Or make the "Changes not staged for commit" part say "new file:
README" ("modified" is implied)
--
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
