Re: Documentation/git-commit.txt

From: Alan Chandler <alan@chandlerfamily.org.uk>
Date: Dec 8, 2006, 22:56 UTC
Message-ID: <200612082256.45456.alan@chandlerfamily.org.uk>
In-Reply-To: <4579529F.9030401@Intel.com>

On Friday 08 December 2006 11:55, Salikh Zakirov wrote:

Show 10 quoted lines

> Junio Hamano wrote:
> > +Instead of staging files after each individual change, you can
> > +tell `git commit` to notice the changes to the tracked files in
> > +your working tree and do corresponding `git add` and `git rm`
> > +for you.
>
> This part is confusing as hell to anyone having any experience
> with either CVS, SVN, Hg or Monotone, as doing "corresponding `git
> add` and `git rm`" commands automatically will be interpreted as
> adding untracked files automatically, which is not the case here.

I thought the wording here was a little weird too. I think this stems from the mistake of saying "tracked files" instead of "tracked content" which then leads to you falling back to the git add and git rm commands..

How about the following wording here

Instead of staging the content of each file immediately after changing it, you can wait until you have completed all the changes you want to make and then use the `-a` option to tell `git commit` to look for all changes to the content it is tracking and commit it automatically. That is, this example ...

-- 
Alan Chandler