Patch tagging/classification

Thomas Petazzoni thomas.petazzoni at
Tue Feb 9 02:18:53 AEDT 2016


On Mon, 8 Feb 2016 15:02:36 +0000, Damien Lespiau wrote:

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

I think it's not a big deal if patchwork sometimes doesn't recognize a
new version of a series as being a new version, and leaves it to the
project admins to mark the old version of the series as superseded

However, it is in my opinion much less acceptable to see patchwork
losing some patches. I'd rather have too much patches in patchwork that
I need to triage/classify/update rather than missing some contributions.

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

More information about the Patchwork mailing list