From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Derrick Stolee <stolee@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [Question] Unicode weirdness breaking tests on ZFS?
Date: Fri, 19 Nov 2021 09:03:42 -0800 [thread overview]
Message-ID: <xmqqmtm0qdqp.fsf@gitster.g> (raw)
In-Reply-To: <20211119154405.xhoqfh3vmljxbh5c@tb-raspi4> ("Torsten Bögershausen"'s message of "Fri, 19 Nov 2021 16:44:05 +0100")
Torsten Bögershausen <tboegi@web.de> writes:
> Should we conclude that the underlying os/zfs is not stable ?
> Things don't seem to be reproducable
>
> What Git needs here in t0050 is that stat("ä") behaves the same as stat("a¨"),
> when either "ä" or "a¨" exist on disk.
> The same for open() and all other file system functions.
We either need to see these two are treated as the same thing, or
these two are treated as two distict filesystem entities, just like
stat("a") and stat("b") are. What we absolutely need is the
unification either always happens or never happens consistently.
I wonder what readdir() is returning. After creat("ä") in an empty
directory, does readdir() in there return "ä" or "a¨? And vice
versa? Is this also inconsistent?
> ("ä" is the precomposed form "a¨" is the decomposed form,
> typically both render to the same glyph on the screen,
> and a hex dump or xxd will show what we had.
> I just use this notation here for illustration)
>
> Should we contact the zfs developers ?
next prev parent reply other threads:[~2021-11-19 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 15:17 [Question] Unicode weirdness breaking tests on ZFS? Derrick Stolee
2021-11-17 15:41 ` Ævar Arnfjörð Bjarmason
2021-11-17 16:12 ` Torsten Bögershausen
2021-11-17 17:06 ` Torsten =?unknown-8bit?Q?B=C3=B6gershausen?=
2021-11-17 17:39 ` Torsten =?unknown-8bit?Q?B=C3=B6gershausen?=
2021-11-17 18:29 ` Derrick Stolee
2021-11-17 18:35 ` Derrick Stolee
2021-11-19 15:44 ` Torsten Bögershausen
2021-11-19 17:03 ` Junio C Hamano [this message]
2021-11-19 18:30 ` Derrick Stolee
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=xmqqmtm0qdqp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).