[PATCH] [RFC] Don't aim to have patchwork send email

Daniel Axtens dja at axtens.net
Thu Feb 22 02:07:46 AEDT 2018

Applied to master: 3cfe618e5e8f9f079713324442c7c0777d2a7bcd


Andrew Donnellan <andrew.donnellan at au1.ibm.com> writes:

> On 15/02/18 12:04, Daniel Axtens wrote:
>> Getting things like SPF and DKIM right for this would be nigh-on
>> impossible, plus it would mean sysadmins would have to let patchwork
>> send email, which is a risk to the reputation of their systems.
>> Let's just aim for being a read-only representation of the mailing
>> list for now.
>> Signed-off-by: Daniel Axtens <dja at axtens.net>
> Reviewed-by: Andrew Donnellan <andrew.donnellan at au1.ibm.com>
> More broadly: should Patchwork move in the direction of being more than 
> a status tracker? I think there's some interesting tools that could be 
> developed to make the life of a developer easier when it comes to 
> actually conducting the activity of code review itself with patches - 
> but (a) I'm not sure Patchwork is the right place to do that, (b) we now 
> expose an API which could be very useful for building such tools 
> separately while utilising all the existing email handling logic in 
> Patchwork, and (c) we already have enough of a backlog when it comes to 
> fixing bugs and adding new features relating to the core job of just 
> tracking emails.
> -- 
> Andrew Donnellan              OzLabs, ADL Canberra
> andrew.donnellan at au1.ibm.com  IBM Australia Limited

More information about the Patchwork mailing list