From: tboegi@web.de
To: tboegi@web.de, git@vger.kernel.org, curtis.allen.smith@gmail.com
Subject: [PATCH/RFC 0/1] More cs/read-cache-conversion-size
Date: Mon, 26 Oct 2026 20:25:14 +0100 [thread overview]
Message-ID: <20261026192514.15844-1-tboegi@web.de> (raw)
In-Reply-To: <xmqqwm1no29m.fsf@gitster.g>
From: Torsten Bögershausen <tboegi@web.de>
Add an addition on top off
cs/read-cache-conversion-size
It turns out that we can optimize even more here.
Torsten Bögershausen (1):
read-cache: optimize file size change when conversion is active
read-cache.c | 19 ++++++++-----------
1 file changed, 8 insertions(+), 11 deletions(-)
--
2.53.0.154.g7c02d39fc2
next prev parent reply other threads:[~2026-10-26 19:25 UTC|newest]
Thread overview: 23+ 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
2026-10-13 17:57 ` Curtis Smith
2026-10-13 18:01 ` Torsten Bögershausen
2026-10-13 18:02 ` [PATCH v5] " Curtis Allen Smith
2026-10-13 20:29 ` Junio C Hamano
2026-10-18 11:18 ` Torsten Bögershausen
2026-10-19 5:57 ` Junio C Hamano
2026-10-20 20:56 ` Torsten Bögershausen
2026-10-26 19:25 ` tboegi [this message]
2026-10-26 19:25 ` [PATCH/RFC 1/1] read-cache: optimize file " tboegi
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=20261026192514.15844-1-tboegi@web.de \
--to=tboegi@web.de \
--cc=curtis.allen.smith@gmail.com \
--cc=git@vger.kernel.org \
/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