From: Phillip Wood <phillip.wood123@gmail.com>
To: Curtis Allen Smith <curtis.allen.smith@gmail.com>, git@vger.kernel.org
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v4] read-cache: do not trust a size change when conversion is active
Date: Tue, 13 Oct 2026 10:44:05 +0100 [thread overview]
Message-ID: <ede6ef41-df6f-4912-be31-1c4a5c0a550e@gmail.com> (raw)
In-Reply-To: <20261013065915.879-1-curtis.allen.smith@gmail.com>
Hi Curtis
On 13/10/2026 07:58, Curtis Allen Smith wrote:
> "git status" can report a file as modified while "git diff" and
> "git add" agree that its contents are unchanged:
>
> git init t && cd t
> printf '* text eol=lf\n' >.gitattributes
> printf 'one\ntwo\nthree\n' >file.txt
> git add . && git commit -m init
>
> printf 'one\r\ntwo\r\nthree\r\n' >file.txt
>
> git status --short # -> M file.txt
> git diff # -> empty
> git add file.txt # -> nothing to commit
>
> ie_modified() takes a change in the file's size since the index
> entry was last refreshed as proof that the file is modified, without
> looking at the contents. A size change proves only that the bytes in
> the working tree changed. When the path is subject to conversion
> (the "text" and "eol" attributes, core.autocrlf, a clean filter),
> different bytes can convert to the same blob, as the CRLF rewrite
> above does.
>
> For such a path, fall through to ce_modified_check_fs(), as is
> already done when only the mtime changed. Paths without conversion
> return early as before.
The commit message talks about "git status" but presumably this change
affects the output of "git diff-files" and "git diff-index" as well.
Does this change improve the performance of "git diff" because it
no-longer tries to diff two blobs that are identical after conversion or
is the existing implementation smart enough to avoid that already?
> A follow-up that skips the conversion and the hash when the length
> already rules out a match is ready if wanted. It takes the
> "genuinely modified" rows to 57 ms and 25 ms.
What does that entail? A file that consists of blank lines can double or
halve its length going from '\n' to '\r\n' and vice-versa. Is that range
narrow enough to avoid converting a significant number of "real" changes?
Looking at t0020-crlf.sh none of the existing tests use a separate
repository, so maybe we could avoid that overhead here as well.
Thanks
Phillip
> read-cache.c | 4 +++-
> t/t0020-crlf.sh | 45 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 48 insertions(+), 1 deletion(-)
>
> diff --git a/read-cache.c b/read-cache.c
> index c4cf08a3a..70f4787de 100644
> --- a/read-cache.c
> +++ b/read-cache.c
> @@ -9,6 +9,7 @@
>
> #include "git-compat-util.h"
> #include "config.h"
> +#include "convert.h"
> #include "date.h"
> #include "diff.h"
> #include "diffcore.h"
> @@ -480,7 +481,8 @@ int ie_modified(struct index_state *istate,
> */
> (!S_ISLNK(st->st_mode) || ce->ce_stat_data.sd_size != MAX_PATH) &&
> #endif
> - (S_ISGITLINK(ce->ce_mode) || ce->ce_stat_data.sd_size != 0))
> + (S_ISGITLINK(ce->ce_mode) || ce->ce_stat_data.sd_size != 0) &&
> + !(S_ISREG(st->st_mode) && would_convert_to_git(istate, ce->name)))
> return changed;
>
> changed_fs = ce_modified_check_fs(istate, ce, st);
> diff --git a/t/t0020-crlf.sh b/t/t0020-crlf.sh
> index fd1cae09e..b76c678ce 100755
> --- a/t/t0020-crlf.sh
> +++ b/t/t0020-crlf.sh
> @@ -397,4 +397,49 @@ test_expect_success 'New CRLF file gets LF in repo' '
> test_cmp alllf alllf2
> '
>
> +test_expect_success 'status does not report a CRLF-only rewrite as modified' '
> + git init eol-status &&
> + (
> + cd eol-status &&
> + echo "* text eol=lf" >.gitattributes &&
> + printf "one\ntwo\nthree\n" >file.txt &&
> + git add .gitattributes file.txt &&
> + git commit -m initial &&
> +
> + # a generator rewrites the file with CRLF, same content
> + printf "one\r\ntwo\r\nthree\r\n" >file.txt &&
> + git status --porcelain -uno >actual &&
> + test_must_be_empty actual &&
> + git diff --exit-code &&
> +
> + # a real change is still reported
> + printf "one\r\ntwo\r\nfour\r\n" >file.txt &&
> + git status --porcelain -uno >actual &&
> + echo " M file.txt" >expect &&
> + test_cmp expect actual
> + )
> +'
> +
> +test_expect_success 'status sees through a CRLF rewrite of a file with a lone CR' '
> + git init eol-status-lone-cr &&
> + (
> + cd eol-status-lone-cr &&
> + echo "* text eol=lf" >.gitattributes &&
> + printf "one\rtwo\nthree\n" >file.txt &&
> + git add .gitattributes file.txt &&
> + git commit -m initial &&
> +
> + # "git add" keeps the lone CR and drops the others
> + printf "one\rtwo\r\nthree\r\n" >file.txt &&
> + git status --porcelain -uno >actual &&
> + test_must_be_empty actual &&
> +
> + # the converted length matches the blob, the content does not
> + printf "one\rtwo\nthrEE\r\n" >file.txt &&
> + git status --porcelain -uno >actual &&
> + echo " M file.txt" >expect &&
> + test_cmp expect actual
> + )
> +'
> +
> test_done
prev parent reply other threads:[~2026-10-13 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 19:51 [PATCH v2 1/2] utf8.c: Prepare workaround for iconv under macOS 14/15 tboegi
2026-01-12 4:58 ` Junio C Hamano
2026-01-12 16:25 ` [PATCH v3 0/2] Workaround " tboegi
2026-01-12 16:25 ` [PATCH v3 1/2] utf8.c: Prepare workaround " tboegi
2026-01-12 16:25 ` [PATCH v3 2/2] utf8.c: Enable " tboegi
2026-10-12 17:56 ` [PATCH v3/RFC 0/1] read-cache: do not trust a size change when conversion tboegi
2026-10-12 17:56 ` [PATCH v3/RFC 1/1] read-cache: do not trust a size change when conversion is active tboegi
2026-10-12 19:11 ` Junio C Hamano
2026-10-13 1:29 ` Junio C Hamano
2026-10-13 6:45 ` Curtis Smith
2026-10-13 5:34 ` Johannes Sixt
2026-10-13 6:48 ` Curtis Smith
2026-10-13 6:58 ` [PATCH v4] " Curtis Allen Smith
2026-10-13 9:44 ` Phillip Wood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ede6ef41-df6f-4912-be31-1c4a5c0a550e@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=curtis.allen.smith@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox