linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Chris Mason <clm@fb.com>
Cc: "Eric Sandeen" <sandeen@redhat.com>,
	"Lukáš Czerner" <lczerner@redhat.com>,
	dchinner@redhat.com, xfs@oss.sgi.com,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Separate mailing list for xfstests
Date: Wed, 14 May 2014 16:04:47 +0000	[thread overview]
Message-ID: <20140514160447.GA3974@thunk.org> (raw)
In-Reply-To: <53738597.70305@fb.com>

On Wed, May 14, 2014 at 11:02:47AM -0400, Chris Mason wrote:
> >> linux-fsdevel might seem as a good candidate for it, but still I
> >> think that it deserves a separate ML to point people to.

I'm personally in favor of using linux-fsdevel since it might
encourage more fs developers who aren't using xfstests yet to start
using it.

For example, we started investigating using xfstests to test unionfs,
and pretty quickly found problems.  (I suspect the same problem exists
in AUFS, BTW, but I've been focusing on unionfs because it's simpler
and less scary.)  The patches to enable the use of xfstests to test
unionfs are still pretty rough, but hopefully we'll get those sent to
Dave once they are cleaned up a bit.

					- Ted

  reply	other threads:[~2014-05-14 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 13:20 Separate mailing list for xfstests Lukáš Czerner
2014-05-14 14:52 ` Eric Sandeen
2014-05-14 15:02   ` Chris Mason
2014-05-14 16:04     ` tytso [this message]
2014-05-14 16:50       ` Tyler Hicks
2014-05-14 21:35       ` Dave Chinner
2014-05-15 10:08         ` Lukáš Czerner
2014-05-14 21:46 ` Dave Chinner
2014-05-15 10:09   ` Lukáš Czerner

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=20140514160447.GA3974@thunk.org \
    --to=tytso@mit.edu \
    --cc=clm@fb.com \
    --cc=dchinner@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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).