From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Luk?? Czerner <lczerner@redhat.com>,
fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfstests: new mailing list
Date: Tue, 20 May 2014 07:25:21 +1000 [thread overview]
Message-ID: <20140519212521.GC8554@dastard> (raw)
In-Reply-To: <20140519145541.GA32055@infradead.org>
On Mon, May 19, 2014 at 07:55:41AM -0700, Christoph Hellwig wrote:
> On Sat, May 17, 2014 at 08:19:30AM +1000, Dave Chinner wrote:
> > Renaming the test suite take a lot more work - .e.g renaming/moving
> > source trees and a fixing all the documentation that points to it...
>
> In that case please call the list xfstests - a name different by a
> single character is utterly confusing. And I defintively see some merit
> to the suggestion that we'll just keep the x and allow people to come up
> with a nice backronym for it if they care enough.
What is important is that we have a separate list for the filesystem
test suite we use, not whether the name has an "x" in or not.
Arguing about whether there should or should not be an 'x' in the
mailing list name is just a waste of time - it's not going to make
me change the name of the list....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-05-19 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 4:46 [ANNOUNCE] xfstests: new mailing list Dave Chinner
2014-05-16 5:40 ` Christoph Hellwig
2014-05-16 8:48 ` Lukáš Czerner
2014-05-16 8:53 ` Christoph Hellwig
2014-05-16 8:55 ` Lukáš Czerner
2014-05-16 14:02 ` Calvin Walton
2014-05-16 14:05 ` Theodore Ts'o
2014-05-16 22:19 ` Dave Chinner
2014-05-19 14:55 ` Christoph Hellwig
2014-05-19 21:25 ` Dave Chinner [this message]
2014-05-16 8:55 ` Sedat Dilek
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=20140519212521.GC8554@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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).