From: "Jones, Peter A" <peter.a.jones@intel.com>
To: Joe Perches <joe@perches.com>,
"hpdd-discuss-owner@lists.01.org"
<hpdd-discuss-owner@ml01.01.org>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Is the list moderated or not?
Date: Sat, 22 Nov 2014 15:24:14 +0000 [thread overview]
Message-ID: <D095EA47.77977%peter.a.jones@intel.com> (raw)
In-Reply-To: <1416527288.6651.27.camel@perches.com>
Sorry Joe. This list has traditionally always been moderated but I guess
something was changed at some point (probably when we joined Intel). I
have adjusted the list to be moderated and it behaved as expected in my
tests. Thanks for drawing our attention to this!
On 11/20/14, 3:48 PM, "Joe Perches" <joe@perches.com> wrote:
>On Thu, 2014-11-20 at 15:43 -0800, hpdd-discuss-owner@lists.01.org
>wrote:
>> You must be a subscriber to post to this list. Please make sure you
>> are sending from a subscribed email address.
>
>The linux-kernel MAINTAINERS file has this as a moderated list.
>If it's not moderated, this entry should be changed to subscriber-only.
>
>STAGING - LUSTRE PARALLEL FILESYSTEM
>M: Oleg Drokin <oleg.drokin@intel.com>
>M: Andreas Dilger <andreas.dilger@intel.com>
>L: HPDD-discuss@lists.01.org (moderated for non-subscribers)
>W: http://lustre.opensfs.org/
>S: Maintained
>F: drivers/staging/lustre
>
>If it's really subscriber only, please change the L: line to:
>
>L: HPDD-discuss@lists.01.org (subscribers-only)
>
>
prev parent reply other threads:[~2014-11-22 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.31138.1416527032.9748.hpdd-discuss@lists.01.org>
2014-11-20 23:48 ` Is the list moderated or not? Joe Perches
2014-11-22 15:24 ` Jones, Peter A [this message]
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=D095EA47.77977%peter.a.jones@intel.com \
--to=peter.a.jones@intel.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpdd-discuss-owner@ml01.01.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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