From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Liu Yuan <namei.unix@gmail.com>,
sheepdog@lists.wpkg.org, qemu-block@nongnu.org
Subject: Re: [PATCH 1/1] block: drop moderated sheepdog mailing list from MAINTAINERS file
Date: Tue, 22 Sep 2020 15:19:31 +0200 [thread overview]
Message-ID: <8045dcba-5613-91ab-89dc-e987b30b5c03@redhat.com> (raw)
In-Reply-To: <20200922090147.1993705-2-berrange@redhat.com>
On 9/22/20 11:01 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 from the same sender continues to get stopped for moderation.
>
> MAINTAINERS entries should be responsive and not uneccessarily block
Typo "unnecessarily".
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> 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
>
>
next prev parent reply other threads:[~2020-09-22 13:26 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 ` [PATCH 1/1] block: drop moderated sheepdog mailing list from MAINTAINERS file Daniel P. Berrangé
2020-09-22 13:19 ` Philippe Mathieu-Daudé [this message]
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=8045dcba-5613-91ab-89dc-e987b30b5c03@redhat.com \
--to=philmd@redhat.com \
--cc=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).