From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Allowing posts to cluster-devel@ from non-subscribers
Date: Thu, 27 Jul 2017 10:20:10 +0100 [thread overview]
Message-ID: <89173da6-1880-d363-9cdc-97b426ed6cf4@redhat.com> (raw)
Hi,
I'd like to propose that we open up cluster-devel@ so that non-members
can post to it. My reasoning is:
- User space development has mostly (all?) moved to ClusterLabs lists so
cluster-devel is now largely a gfs2/dlm kernel dev list.
- Kernel patches tend to get cross-posted to cluster-devel as it is
listed in the MAINTAINERS file.
- Patches and patch reviews from kernel developers who don't regularly
work on cluster components get held up in the moderation queue.
- The moderation queue may not get checked for long periods if the
active list moderators are absent.
Are there any strong objections to $subject? If not I'll go ahead and
flip the switch.
Andy
next reply other threads:[~2017-07-27 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:20 Andrew Price [this message]
2017-07-27 9:23 ` [Cluster-devel] Allowing posts to cluster-devel@ from non-subscribers Steven Whitehouse
2017-07-28 13:47 ` Andrew Price
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=89173da6-1880-d363-9cdc-97b426ed6cf4@redhat.com \
--to=anprice@redhat.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).