kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
	linux-pci@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
	linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	linux-mediatek@lists.infradead.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	Pia Eichinger <pia.eichinger@st.oth-regensburg.de>
Subject: Re: [PATCH] MAINTAINERS: make linux-mediatek list remarks consistent
Date: Mon, 14 Sep 2020 14:12:54 +0000	[thread overview]
Message-ID: <7da64c0975c345f1f45034410c9ed7d509ba9831.camel@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2009141552570.17999@felia>

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

On Mon, 2020-09-14 at 16:01 +0200, Lukas Bulwahn wrote:
> > > I am not subscribed to linux-mediatek. When I sent an email to the list,
> > > it showed up really seconds later in the lore.kernel.org of the
> > > linux-mediatek public-inbox repository. So, either it was delivered
> > > quickly as it is not moderated or my check with lore.kernel.org is wrong,
> > > e.g., mails show up in the lore.kernel.org archive, even they were not
> > > yet permitted on the actual list.
> > > 
> > 
> > I'm the moderator and I get requests to moderate emails. I suppose I added you
> > to the accepted list because of earlier emails you send.
> > 
> 
> Okay, I see. I did send some clean-up patch in the past, but I completely 
> forgot that, but my mailbox did not forget. So, now it is clear to me why 
> that mail showed up so quickly.
> 
> Thanks for the explanation.

AFAICT the linux-mediatek list isn't configured to automatically
moderate messages from non-subscribers. Its generic_nonmember_action
setting is 'Accept'. That is the default setting for lists on
infradead.org and I strongly encourage list maintainers to leave it
that way.

Lukas, I don't see your address in the allowlist either.

There are other reasons why some messages get might trapped for
moderation — the message size, number of recipients, spam score, etc.

The mere fact that *some* messages are moderated does not mean that the
list is "moderated for non-subscribers" in the sense that the
MAINTAINERS file lists.

> Bjorn, with that confirmation and Reviewed-by from Matthias, could you 
> please pick this patch?

I think we should be fixing the ones that *do* say it's moderated for
non-subscribers, not the one that correctly didn't :)

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2020-09-14 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:31 [PATCH] MAINTAINERS: make linux-mediatek list remarks consistent Lukas Bulwahn
2020-09-14  5:39 ` Lukas Bulwahn
2020-09-14  9:25 ` Matthias Brugger
2020-09-14 10:20   ` Lukas Bulwahn
2020-09-14 13:11     ` Matthias Brugger
2020-09-14 14:01       ` Lukas Bulwahn
2020-09-14 14:12         ` David Woodhouse [this message]
2020-09-14 14:57           ` Lukas Bulwahn
2020-09-14 15:16             ` David Woodhouse
2020-09-14 15:23               ` Lukas Bulwahn
2020-09-14 15:30                 ` David Woodhouse
2020-09-14 15:31                   ` Lukas Bulwahn
2020-09-14 15:17           ` Lukas Bulwahn
2020-09-15  8:41           ` Matthias Brugger

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=7da64c0975c345f1f45034410c9ed7d509ba9831.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bhelgaas@google.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pia.eichinger@st.oth-regensburg.de \
    --cc=ralf.ramsauer@oth-regensburg.de \
    --cc=ryder.lee@mediatek.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).