[PATCH] Implement list filtering

Daniel Axtens dja at axtens.net
Thu Feb 1 07:39:20 AEDT 2018

Hi all,

>> To be honest, given how simple and generic this patch is, I'd prefer to
>> keep the logic within Patchwork. It would require much less work on an
>> administrators end over all (seeing as they'll have to configure
>> procmail too), and be far more transparent to end users.
> I agree. Our goal is to have Patchwork as a service (container or VM)
> managed by DevOps or similar team. This solution would make it uselessly
> hard to for example add and edit projects -- instead of having our
> Patchwork admin user click a few times, we would need to contact those
> people and explain to them how to change the configuration with every
> change we need. And as Stephen said, it's really not a straightforward
> and transparent solution.

OK, sold on the PW solution now. Will look at the code itself shortly.


> Veronika
>> Thoughts?
>> Stephen
>> _______________________________________________
>> Patchwork mailing list
>> Patchwork at lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/patchwork

More information about the Patchwork mailing list