linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: tytso@mit.edu, Chris Mason <clm@fb.com>,
	Eric Sandeen <sandeen@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: Thu, 15 May 2014 12:08:10 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1405151207150.2112@localhost.localdomain> (raw)
In-Reply-To: <20140514213529.GT26353@dastard>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1636 bytes --]

On Thu, 15 May 2014, Dave Chinner wrote:

> Date: Thu, 15 May 2014 07:35:29 +1000
> From: Dave Chinner <david@fromorbit.com>
> To: tytso@mit.edu
> Cc: Chris Mason <clm@fb.com>, 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
> 
> On Wed, May 14, 2014 at 04:04:47PM +0000, tytso@mit.edu wrote:
> > 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.
> 
> I'd prefer a separate mailing list - I don't really like the idea of
> burying general lists in large amounts of specific topic-related
> traffic. That way lies lkml - a dumping ground for everything that
> has no stopic-related lists and that results in a very low signal to
> noise ratio. Comparitively speaking, -fsdevel has a high SNR, so we
> should try to keep it that way. ;)
> 
> That said, I can see the value in sending update/release
> announcements to -fsdevel, but I'd prefer to keep all the xfstests
> traffic separate.  A separate list makes things like archive
> searching and patch tracking much simpler....

I agree, having a separate list and sending out update/release
announcements to fsdevel sounds like the best solution to me.

Thanks!
-Lukas

> 
> Cheers,
> 
> Dave.
> 

  reply	other threads:[~2014-05-15 10:08 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
2014-05-14 16:50       ` Tyler Hicks
2014-05-14 21:35       ` Dave Chinner
2014-05-15 10:08         ` Lukáš Czerner [this message]
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=alpine.LFD.2.00.1405151207150.2112@localhost.localdomain \
    --to=lczerner@redhat.com \
    --cc=clm@fb.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    --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).