linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Lukáš Czerner" <lczerner@redhat.com>, dchinner@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: Separate mailing list for xfstests
Date: Wed, 14 May 2014 09:52:06 -0500	[thread overview]
Message-ID: <53738316.20601@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1405141508150.9727@localhost.localdomain>

On 5/14/14, 8:20 AM, Lukáš Czerner wrote:
> Hi Dave,
> 
> I am wondering whether you're open to the idea of creating separate
> mailing list for xfstests. It is no longer xfs specific project and
> even though you're still a maintainer of the project, other fs folks
> are definitely interested in the development process, but not
> everyone might be interested in receiving everything from the
> xfs@oss.sgi.com list.
> 
> To speak for myself I would like to help with review of xfstests
> patches as well, but I rarely go through my xfs folder
> unfortunately.
> 
> linux-fsdevel might seem as a good candidate for it, but still I
> think that it deserves a separate ML to point people to.
> 
> What do you think ?

That sounds pretty reasonable to me.  We've always encouraged submissions
to cc: the other relevant lists (i.e. linux-ext4 if it's an ext4-specific
patch) and would probably still encourage that, but even from the other
angle (keeping i.e. ext4-specific and btrfs-specific patches off the
xfs list) this sounds like a good idea.

-Eric

> Thanks!
> -Lukas

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-05-14 14:52 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 [this message]
2014-05-14 15:02   ` Chris Mason
2014-05-14 16:04     ` tytso
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=53738316.20601@redhat.com \
    --to=sandeen@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=lczerner@redhat.com \
    --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).