lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 14 May 2014 11:02:47 -0400
From:	Chris Mason <clm@...com>
To:	Eric Sandeen <sandeen@...hat.com>,
	Lukáš Czerner 
	<lczerner@...hat.com>, <dchinner@...hat.com>
CC:	<xfs@....sgi.com>, <linux-fsdevel@...r.kernel.org>,
	<linux-ext4@...r.kernel.org>
Subject: Re: Separate mailing list for xfstests



On 05/14/2014 10:52 AM, Eric Sandeen wrote:
> 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@....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.

+1 here.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ