Per-project sender blacklist

[ajdlinux]

Sometimes we want to block patches from certain senders (e.g. bots that are irrelevant for a certain kernel subsystem but end up Cc-ing them anyway) from appearing as patches in patchwork.

Would be helpful to be able to block these patches on a per-project basis so that different maintainers can make different decisions.

(@mpe)

[stephenfin]

Would this be done via Patchwork or something like Mailman?

[ajdlinux]

To be clear - at a Patchwork level. It's not that we want to block senders from the mailing list, just that we don't necessarily care about tracking them in Patchwork.

[ajdlinux]

(@mpe considers this very low priority but it came up in a conversation we had as a feature that would be mildly useful)

[daxtens]

You could also do it in a pre-patchwork filter script. OzLabs definitely has one because it caused an issue we mistakenly thought was ours.

…

On Thu, Nov 7, 2019 at 3:28 PM Andrew Donnellan ***@***.***> wrote: ***@***.*** <https://github.com/mpe> considers this very low priority but it came up in a conversation we had as a feature that would be mildly useful) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#323?email_source=notifications&email_token=AAZHSBMB5CQX4D4YMHKCTETQSOKN7A5CNFSM4JJOD4JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDJUOKQ#issuecomment-550717226>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZHSBNZJUBVCIAHFCVBDMTQSOKN7ANCNFSM4JJOD4JA> .

[mpe]

Daniel Axtens <notifications@github.com> writes:

You could also do it in a pre-patchwork filter script. OzLabs definitely has one because it caused an issue we mistakenly thought was ours.

You could, but that's basically just hacking around the lack of the feature in patchwork :) cheers

[daxtens]

Fair point.

…