From: Adam Dinwoodie <adam@dinwoodie.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org,
Lessley Dennington <lessleydennington@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] t9902: split test to run on appropriate systems
Date: Mon, 2 May 2022 15:46:10 +0100 [thread overview]
Message-ID: <20220502144610.fyxns33cfrpa5gsy@lucy.dinwoodie.org> (raw)
In-Reply-To: <20220409153626.qqn23c7vsw4ftges@lucy.dinwoodie.org>
On Sat, Apr 09, 2022 at 04:36:26PM +0100, Adam Dinwoodie wrote:
> On Fri, Apr 08, 2022 at 12:56:30PM +0200, Ævar Arnfjörð Bjarmason wrote:
> >
> > <snip>
> >
> > I converted all the straightforward cases, where these tests were either
> > a bit misleading, or we'd actually skip testing on some systems
> > needlessly e.g. if they supported \t in a name but not \n.
> >
> > This leaves only 8 remaining cases of FUNNYNAMES, all of those similarly
> > seem like subtle potential issues. I.e. we're creating files with
> > characters like "?" or "*" in the name.
> >
> > But the prerequisite never checks for that, we're just implicitly
> > assuming that a FS that can do [\t\n"] an also do [*?+] or whatever.
> >
> > In the case of the "rm" test we'd unconditionally create a file with a
> > space in its name, but then conditional on FUNNYNAMES remove it.
> >
> > <snip>
>
> That's a significantly neater patch than I was expecting! I can see
> Junio's added my quick fix for the v2.36.0 rc; what's the process from
> here in this circumstance? Wait for v2.36.0 to be released properly,
> then submit the patches?
>
> Fixing t9902 using the same scheme as above adds the diff below, after
> applying the patch above to the v2.36.0-rc1 tag; I've confirmed this
> works as expected on Cygwin, with the test gated by FS_NAME_TAB passing
> and the test gated by FS_NAME_BACKSLASH being skipped.
>
> <snip>
Ævar, are you able to submit your patch here to provide the better
long-term fix? Once you've submitted your signed-off version, I can
submit the t9902-specific changes on top, or I'm happy for you to just
integrate them into your commit if that's easier.
prev parent reply other threads:[~2022-05-02 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 9:53 [PATCH] t9902: split test to run on appropriate systems Adam Dinwoodie
2022-04-08 10:56 ` Ævar Arnfjörð Bjarmason
2022-04-09 15:36 ` Adam Dinwoodie
2022-05-02 14:46 ` Adam Dinwoodie [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=20220502144610.fyxns33cfrpa5gsy@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=lessleydennington@gmail.com \
--cc=newren@gmail.com \
/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).