git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: A new feature command request `cmd_ignore`

From
Johannes Sixt <j6t@kdbg.org>
Date
Jan 15, 2022, 09:03 UTC
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:
Show 6 quoted lines
> 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
Previous: Elijah NewrenNext: Jaydeep Das
Message 3 of 5 in “A new feature command request `cmd_ignore`”
  1. Jaydeep DasJan 14, 2022
  2. Elijah NewrenJan 15, 2022
  3. Johannes SixtJan 15, 2022
  4. Jaydeep DasJan 15, 2022
  5. Johannes SixtJan 15, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.