From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Zach Brown <zab@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfstests names/numbers
Date: Thu, 17 Oct 2013 08:49:38 +1100 [thread overview]
Message-ID: <20131016214938.GJ4446@dastard> (raw)
In-Reply-To: <525EBDD1.7070107@sandeen.net>
On Wed, Oct 16, 2013 at 11:24:49AM -0500, Eric Sandeen wrote:
> Hey all (probably specifically Dave) -
>
> Is there any patch in the works to allow non-numeric test names?
> It'd be nice to get away from the nondescript numbers clashing.
Well, I was kind of waiting for the rest of Lukas' patch that
introduced config sections to be finished and committed before
touching that same code...
> The numeric names "in service of nothing" is making Zach unhappy.
>
> And if Zach ain't happy, ain't nobody happy. ;)
On the count of 3. 1... 2... 3...
Awwwwww, poor Zach.
:)
> But seriously, I think that was in the works, or in the plan,
> once. Is there a patch out there somewhere?
There's a bit of infrastructure work to make it a reality - all of
the CLI parsing/validity checks assumes tests are numbered and match
a sepcific regex, as do some of the test list building functions.
That all needs to be reworked, and up until now it hasn't been a
huge priority for me so I haven't started that work yet.
You're more than welcome to hack on it if you want....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-16 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 16:24 xfstests names/numbers Eric Sandeen
2013-10-16 16:49 ` Zach Brown
2013-10-16 21:49 ` Dave Chinner [this message]
2013-10-16 22:46 ` Zach Brown
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=20131016214938.GJ4446@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=zab@redhat.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