Re: [PATCH] Documentation/git-commit: rewrite to make it more end-user friendly.

From: J. Bruce Fields <bfields@fieldses.org>
Date: Dec 10, 2006, 21:00 UTC
Message-ID: <20061210210057.GB23387@fieldses.org>
In-Reply-To: <200612100130.48812.Josef.Weidendorfer@gmx.de>

On Sun, Dec 10, 2006 at 01:30:47AM +0100, Josef Weidendorfer wrote:

Show 10 quoted lines

> On Saturday 09 December 2006 06:48, Junio C Hamano wrote:
> > +1. by using gitlink:git-add[1] to incrementally "add" changes to the
> > +   next commit before using the 'commit' command (Note: even modified
> > +   files must be "added");
> 
> Regarding this note: Of course unmodified files do not have to be added ;-)
> 
> What about: "(Note: changes in files already known to git, and even new
> changes done after a previous `git add` for a given file, still must
> be staged again)"

Or maybe: "by using gitlink:git-add[1] to add new content (of either new or newly modified files) to the next commit."

Man pages are reference documentation, so I figure it's OK to sacrifice a little newbie-friendliness for accuracy and concision.

I dunno, I think basically the right content is there and Junio should just commit it (after the git-rm change?), and then allow the rest of us nitpickers to submit patches against the result to our heart's content....