Patch tagging/classification

Damien Lespiau damien.lespiau at
Mon Feb 8 23:45:50 AEDT 2016

On Sun, Feb 07, 2016 at 04:02:40PM +0100, Thomas Petazzoni wrote:
> Hello,
> I don't remember if I already suggested this feature, or if it has been
> suggested in the past already. If that's the case, then sorry for the
> duplicate.
> Over at the Buildroot project, we often handle a fairly long queue of
> patches in our patchwork, currently around 350+ patches. One thing that
> I'm missing is a way of triaging/tagging the patches, like which ones
> are for the current release, which ones are clearly for the next
> release, etc. Each project probably has different
> tagging/classification needs.

That idea has been floating around indeed. That's something I want as

I'm leaning towards some key/value pair associated with patches and
revisions, allowing the key to be null for simple tagging.


More information about the Patchwork mailing list