From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Liu Yuan" <namei.unix@gmail.com>,
sheepdog@lists.wpkg.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org
Subject: [PATCH 1/1] block: drop moderated sheepdog mailing list from MAINTAINERS file
Date: Tue, 22 Sep 2020 10:01:47 +0100 [thread overview]
Message-ID: <20200922090147.1993705-2-berrange@redhat.com> (raw)
In-Reply-To: <20200922090147.1993705-1-berrange@redhat.com>
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 from 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(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3d17cad19a..8e8a4fb0a8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2852,7 +2852,6 @@ F: block/rbd.c
Sheepdog
M: Liu Yuan <namei.unix@gmail.com>
L: qemu-block@nongnu.org
-L: sheepdog@lists.wpkg.org
S: Odd Fixes
F: block/sheepdog.c
--
2.26.2
next prev parent reply other threads:[~2020-09-22 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:01 [PATCH 0/1] block: future of sheepdog storage driver ? Daniel P. Berrangé
2020-09-22 9:01 ` Daniel P. Berrangé [this message]
2020-09-22 13:19 ` [PATCH 1/1] block: drop moderated sheepdog mailing list from MAINTAINERS file Philippe Mathieu-Daudé
2020-09-22 10:32 ` [PATCH 0/1] block: future of sheepdog storage driver ? Thomas Huth
2020-09-22 13:25 ` Markus Armbruster
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=20200922090147.1993705-2-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).