Re: [PATCH 01/10] Better "Changed but not updated" message in git-status

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Oct 30, 2010, 04:00 UTC
Message-ID: <vpqlj5gxrbb.fsf@bauges.imag.fr>
In-Reply-To: <1288386368.7988.22.camel@drew-northup.unet.maine.edu>

Drew Northup <drew.northup@maine.edu> writes:

Show 16 quoted lines

> On Thu, 2010-10-28 at 17:09 -0500, Jonathan Nieder wrote:
>> 
>> # Changes to be committed:
>> #   (use "git reset -- <path>..." to unstage)
>> #
>> #	new file:    foo.c
>> #
>> # Changes not to be committed:
>> #   (use "git add <path>..." to update what will be committed)
>> #   (use "git checkout -- <path>..." to discard changes in working
>> #   directory)
>> #
>> #	typechange:  bar.c
>
> This one gets my vote out of the replacements I've seen. I appreciate
> leaving the "git add" idiom untouched.

I still prefer my version. "Not staged for commit" makes it clearer that the files appear in this section because the user did not do some action (stage), while "not to be commited" remains a bit more misterious about the reason why the changes will not be commited, and mentionning the word "stage" here somehow teaches the user what staging means in the Git world.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/