From: Johannes Sixt <j6t@kdbg.org>
Date: Sat, 15 Jan 2022 09:03:46 GMT
Subject: Re: A new feature command request `cmd_ignore`
Message-ID: <5f6f1dba-a923-4bb9-70a7-4936566f46e0@kdbg.org>
In-Reply-To: <CABPp-BFY2issEqOj1Oj71k=494vc8E563CndxPZfXYrteFoNhw@mail.gmail.com>

Am 15.01.22 um 06:17 schrieb Elijah Newren:
> On Fri, Jan 14, 2022 at 3:03 PM Jaydeep Das <jaydeepjd.8914@gmail.com> wrote:
>> and other parameters like `--force`
>> could be added which would delete that file cache if that
>> file was already committed.
> 
> I don't understand what you mean by this.

I think that is a paraphrase of the suggestion to

   git rm --cached settings
   echo settings >> .gitignore

when changes to a file 'settings' that was already tracked (and often
contains user-specific settings) should be ignored. This misguided and
short-sighted "solution" is repeated numerous times on Stackoverflow.
Not something that we should encourage.

-- Hannes