From: "Theodore Ts'o" <tytso@mit.edu>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
"Christoph Hellwig" <hch@infradead.org>,
"Dave Chinner" <david@fromorbit.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: Fri, 16 May 2014 10:05:23 -0400 [thread overview]
Message-ID: <20140516140523.GA20683@thunk.org> (raw)
In-Reply-To: <1400248927.979.2.camel@sasami.ottawa.blindsidenetworks.com>
On Fri, May 16, 2014 at 10:02:07AM -0400, Calvin Walton wrote:
>
> Instead of renaming the test suite, why not just "backronym" it to mean
> something different? The letter x is used to mean "cross" in many
> contexts, so "xfstests" could easily mean "cross-filesystem tests" - a
> name that fits perfectly!
Or maybe "extended file system tests", if people really are concerned
about the naming. Seriously, is this really that important to folks?
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: fstests@vger.kernel.org, xfs@oss.sgi.com,
"Christoph Hellwig" <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
"Lukáš Czerner" <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfstests: new mailing list
Date: Fri, 16 May 2014 10:05:23 -0400 [thread overview]
Message-ID: <20140516140523.GA20683@thunk.org> (raw)
In-Reply-To: <1400248927.979.2.camel@sasami.ottawa.blindsidenetworks.com>
On Fri, May 16, 2014 at 10:02:07AM -0400, Calvin Walton wrote:
>
> Instead of renaming the test suite, why not just "backronym" it to mean
> something different? The letter x is used to mean "cross" in many
> contexts, so "xfstests" could easily mean "cross-filesystem tests" - a
> name that fits perfectly!
Or maybe "extended file system tests", if people really are concerned
about the naming. Seriously, is this really that important to folks?
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-16 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 4:46 [ANNOUNCE] xfstests: new mailing list Dave Chinner
2014-05-16 4:46 ` Dave Chinner
2014-05-16 5:40 ` Christoph Hellwig
2014-05-16 5:40 ` Christoph Hellwig
2014-05-16 8:48 ` Lukáš Czerner
2014-05-16 8:48 ` Lukáš Czerner
2014-05-16 8:53 ` Christoph Hellwig
2014-05-16 8:53 ` Christoph Hellwig
2014-05-16 8:55 ` Lukáš Czerner
2014-05-16 8:55 ` Lukáš Czerner
2014-05-16 14:02 ` Calvin Walton
2014-05-16 14:02 ` Calvin Walton
2014-05-16 14:02 ` Calvin Walton
2014-05-16 14:05 ` Theodore Ts'o [this message]
2014-05-16 14:05 ` Theodore Ts'o
2014-05-16 22:19 ` Dave Chinner
2014-05-16 22:19 ` Dave Chinner
2014-05-19 14:55 ` Christoph Hellwig
2014-05-19 14:55 ` Christoph Hellwig
2014-05-19 21:25 ` Dave Chinner
2014-05-19 21:25 ` Dave Chinner
2014-05-16 8:55 ` Sedat Dilek
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=20140516140523.GA20683@thunk.org \
--to=tytso@mit.edu \
--cc=calvin.walton@kepstin.ca \
--cc=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 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.