Feature request: tracking of patches that are -stable candidates

[Theodore Tso]

On Mon, Sep 29, 2008 at 06:53:44PM +1000, Jeremy Kerr wrote:
> One thing I was thinking about is tags - kind of like the current 
> states, but a patch can have more than one tag. Tags would differ from 
> bundles in that:
> 
>  * tags are global to all users (bundles being per-user)
>  * the tags on a patch would appear on the patch page
> 
> We could use a similar interface to bundles - public pages to list the 
> patches that have a particular tag, downloadable as an mbox.
> 
> How does that sound?

Yep, that sounds like just the thing!  It's flexible enough that I can
also use a tag for "in the ext4 patch queue", which is something that
can be independent of whether a patch is under review or not.

(I tend to be put things in the ext4 patch queue early so I can do
things like edit the description for parsability by native English
speakers early on.  If there was a way to edit the patches description
early, and there some way that the mainainer could publish a global
bundle, and there was some way of specifying the order of patches that
appear in a bundle, patchwork might completely obviate the need for
the ext4 patch queue.  I'm not sure you're interested in taking
patchwork in that direction, but if you were, that would be great.
For now, I'm using patchwork as an adjunct to the ext4 patch queue[1],
which is nothing more than a repository containing a quilt series
files plus the patch files.  It works pretty well for us, but it would
really convenient if patchwork could take over that function!)

[1] http://repo.or.cz/w/ext4-patch-queue.git 

							- Ted