From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] precompose_utf8: use a flex array for d_name
Date: Fri, 03 Jul 2026 01:39:54 -0700 [thread overview]
Message-ID: <xmqq8q7sjwkl.fsf@gitster.g> (raw)
In-Reply-To: <20260703050800.GA29216@tb-raspi4> ("Torsten Bögershausen"'s message of "Fri, 3 Jul 2026 07:08:00 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> Nice, thanks for the patch. One minor nit/question: Do we need a
> test_have_prereq PERL in t/t3910 ?
Good question.
>> +test_expect_success "status with long non-ASCII filename" '
>> + test_when_finished "rm -rf long-utf8-status" &&
>> + git init long-utf8-status &&
>> + (
>> + cd long-utf8-status &&
>> + test "$(git config --bool core.precomposeunicode)" = true &&
>> + long_utf8_name=$(
>> + perl -e "print q(a) x 249, qq(\342\200\224) x 3, q(.md)"
>> + ) &&
>> + test "$(printf "%s" "$long_utf8_name" | wc -c | tr -d " ")" = 261 &&
>> + printf "content\n" >"$long_utf8_name" &&
I would say that if we are going to use this construct as-is, then
we do need the prereq.
But as far as I can see, this is mostly to create a very long
filename, which does not require perl at all, with 9 bytes of binary
which could be easily done with printf with the ame backslash
notation.
So, if we can fix the test, that would be preferrable.
Thanks.
>> + git status --porcelain=v1 >actual
>> + )
>> +'
>> +
>> test_expect_failure 'handle existing decomposed filenames' '
>> echo content >"verbatim.$Adiarnfd" &&
>> git -c core.precomposeunicode=false add "verbatim.$Adiarnfd" &&
>>
next prev parent reply other threads:[~2026-07-03 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 2:35 [PATCH] precompose_utf8: use a flex array for d_name Ihar Hrachyshka
2026-07-03 5:08 ` Torsten Bögershausen
2026-07-03 8:39 ` Junio C Hamano [this message]
2026-07-03 8:40 ` Patrick Steinhardt
2026-07-03 20:20 ` Ihar Hrachyshka
2026-07-04 23:37 ` [PATCH v2] " Ihar Hrachyshka
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=xmqq8q7sjwkl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ihar.hrachyshka@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.