Patch tagging/classification

Ruslan Kuprieiev kupruser at
Tue Feb 9 02:19:37 AEDT 2016

On 02/08/2016 05:02 PM, Damien Lespiau wrote:
> On Mon, Feb 08, 2016 at 04:39:15PM +0200, Ruslan Kuprieiev wrote:
>> Hi Damien,
>> That looks great!
>> Is it a pure pwclient you are using?
> This is a different version of patchwork that I maintain for our own use
> (I'm part of the i915 kernel team at Intel). That version is deployed on
> The series support is done when emails are parsed by patchwork,
> reconstructing email threads and creating series/revisions/patches
> objects instead of merely patches objects.
> An interesting point is that series objects aggregate the initial
> submission, but also subsequent updates. A bit more details on what is
> supported:
> Now, I can't stress enough that I still need to iron out some corner
> cases. There also are cases where it's ambiguous what the sender is
> trying to do. Parsing the intention of the submitter is hard, people
> will do the strangest things. I think I'd like to see a tool to wrap git
> send-email, that would ensure a more deterministic way of sending
> patches and updates after review see:
> That said, we've been using the series support for a few months already
> with a CI system that take full series of patches for testing and gives
> test results back. So it's already somewhat useful, if you don't mind
> the hiccups too much (which can lead to patchwork losing some patches).

It looks fantastic, and it is exactly what I've been looking for for a 
long time now.
Why aren't these features merged into base patchwork yet?

How hard can it be to use your patchwork version for another project?
I'm participating in CRIU[1] project and we would love to try your 
patchwork mod.

Corner cases are fine, I tried writing my own tool for mailing list 
patch tester some
time ago and also did run into a number of corner cases and eventually 
decided to
disable it to find a better solution.



More information about the Patchwork mailing list