Adding custom tags like bugzilla id to patches

Don Zickus dzickus at
Thu Jan 4 14:07:04 AEDT 2018

On Wed, Jan 03, 2018 at 11:54:05AM -0500, Aaron Conole wrote:
> Don Zickus <dzickus at> writes:
> > On Wed, Jan 03, 2018 at 11:23:43AM +1100, Andrew Donnellan wrote:
> >> On 03/01/18 08:31, Don Zickus wrote:
> >> > I wanted to add a custom tag to patchwork, for example 'Bugzilla:' that
> >> > would store the bugzilla id.  This id could be queried later and added at
> >> > mbox creation time.
> >> > 
> >> > Most tags revolve around 'counts' and are generated on the fly
> >> > (refresh_tag_counts).  Not sure if bugzilla id fits in that model?
> >> What exactly would you want to do with these tags - expose them through the
> >> filter interface?
> >
> > Block patches from being accepted unless the bugzilla was approved.  So the
> > patch-ready script would use it and it would be exposed inside the patch web
> > page as a tag with a web link to the bugzilla.  The bugzilla would also be
> > used in a git commit hook to populate our errata.
> >
> > Process stuff..
> So, there is the ability to add arbitrary tags to the patchwork database
> for it to track.  But, I think what doesn't exist is Andrew's suggestion
> / question about searching for patches by tag values.  Probably that is
> the feature that would be needed to accomplish what you are looking for?

Actually thinking about it some more.  Yeah, I can create arbituary tags
today.  But they somehow automatically go on the webUI.  Probably would want
to skip that.  Need to query for the tag values.  Would be interested in
creating random ones through an api too. So..

* skip tag from showing up on webUI
* ability to query for tag and its value (ie bugzilla->1234)
* ability to add random tag for tracking purposes (build-id->5678)
  - doesn't necessary come through email, but through api??
* display tags on patch webpage



More information about the Patchwork mailing list