From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org,
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
Jeff Cody <jcody@redhat.com>, Liu Yuan <namei.unix@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: drop moderated sheepdog mailing list from MAINTAINERS file
Date: Wed, 21 Mar 2018 10:42:57 -0500 [thread overview]
Message-ID: <880c56f0-0ae6-c579-5345-1f9637dcf07e@redhat.com> (raw)
In-Reply-To: <20180321153124.5357-1-berrange@redhat.com>
On 03/21/2018 10:31 AM, Daniel P. Berrangé wrote:
> The sheepdog mailing list is setup to stop and queue messages from
> non-subscribers, pending moderator approval. Unfortunately it seems
> that the moderation queue is not actively dealt with. Even when messages
> are approved, the sender is never added to the whitelist, so every
> future mail the same sender continues to get stopped for moderation.
>
> MAINTAINERS entries should be responsive and not uneccessarily block
> mails from QEMU contributors, so drop the sheepdog mailing list.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
Perhaps the sheepdog list would like to know what we are doing, along
with a heads up that their list policy is unfriendly. But I can't be
the one to tell them - if I were to add the sheepdog list in cc, I'd get
moderated.
It's annoyed me enough times that I agree with the change.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-21 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 15:31 [Qemu-devel] [PATCH] block: drop moderated sheepdog mailing list from MAINTAINERS file Daniel P. Berrangé
2018-03-21 15:34 ` Jeff Cody
2018-03-21 15:42 ` Eric Blake [this message]
2018-03-21 15:45 ` Daniel P. Berrangé
2018-10-19 11:25 ` Daniel P. Berrangé
2018-10-19 11:41 ` Philippe Mathieu-Daudé
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=880c56f0-0ae6-c579-5345-1f9637dcf07e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=jcody@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).