Re: first para of man gitignore should refer to 'git rm --cached'

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Nov 8, 2010, 04:46 UTC
Message-ID: <AANLkTinznLY3M4z7k-WeeFhGSR1xWHXj_zOrwMvZDfLQ@mail.gmail.com>
In-Reply-To: <20101107191425.GA32302@kytes>

On Mon, Nov 8, 2010 at 12:44 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 11 quoted lines

> Hi Sitaram,
>
> Sitaram Chamarty writes:
>> It's an FAQ that "why doesn't my gitignore work" when the files in
>> question had already been added earlier, usually in error.  The most
>> common remedy, I believe, is "git rm --cached" followed by a commit.
>
> Er, no. The documentation says "in order to ignore uncommitted changes
> in already tracked files". `git rm --cached` removes the file from the
> index altogether- when the change is committed, Git will actually stop
> tracking it.

I agree.

I'm just saying that ignoring uncommitted changes to already tracked files is *not* the most common question I see when it comes to gitignore, and am asking if it is worth putting what I believe is the real FAQ in the first para, and move the assume-unchanged stuff further down the page.

Sorry if I didn't say that clearly enough before.