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

Re: git filter bug

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 13, 2022, 17:29 UTC
Message-ID
<xmqqsfo879r7.fsf@gitster.g>
In-Reply-To
<442e3166-4f18-3ee0-e3bc-d24687471d5c@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
> git status does not compute differences; it only looks at the stat
> information, and that is by design for performance reasons. So, IMO,
> this is working as designed and not a bug.

Hmph, is that true? I thought "git status" did an equivalent of diff.autoRefreshIndex just like other commands like "git diff" at the Porcelain level.

Is this more like the commonly seen "after you futzed the attributes to affect normalization, "--renormalize" is needed to force the index to match the cleaned version of working tree under the new clean filter rules", I wonder?

Previous: Johannes SixtNext: Johannes Sixt
Message 3 of 6 in “git filter bug”
  1. Udoff, MarcJun 10, 2022
  2. Johannes SixtJun 11, 2022
  3. Junio C HamanoJun 13, 2022
  4. Johannes SixtJun 13, 2022
  5. Shupak, VitalyJun 14, 2022
  6. Udoff, MarcJun 23, 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.