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



On 14/09/2020 16:12, David Woodhouse wrote:
> 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.

Ok, thanks for clarification. I never bothered too much with all the 
configuration option of the list. :|

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

I tried to find that in the web interface, but wasn't able to find the list.

Regards,
Matthias

> 
> 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 :)
> 

      parent reply	other threads:[~2020-09-15  8:42 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
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 [this message]

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=14193442-3b41-29f2-4380-e2cbcc00e5d4@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dwmw2@infradead.org \
    --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=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).