Hi Stephen,
> Is there anyway to get statistics out of patchwork about how long
> patches sit around, reject/accept rates, and patch sizes?
There's no exposed interface for stats at present, but if it's a
once-off on patchwork.ozlabs.org I'm happy to do a query. For more
general stuff, we can cer
Is there anyway to get statistics out of patchwork about how long patches sit
around,
reject/accept rates, and patch sizes?
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
> Yeah, there was a question on this here on the ML just last week [1].
> The solution proposed - create a patchwork account - does seem like
> overkill.
Yes and no. It could be worse, but asking a random patch developer to
register at a (for the developer) random site because it makes my
workflo
Hello,
On Tue, 22 Mar 2016 15:09:23 +, Finucane, Stephen wrote:
> Actually, I stand corrected. Doing the above would require the 'Label'
> model having a many-to-many relationship with both a 'Project' and a
> 'Patch'. There doesn't seem to be any way to enforce this at the ORM
> level, and i
On 15 Mar 22:04, Arnout Vandecappelle wrote:
> >I'm waiting on reviews for cover letter feature, so I've picked this up
> >as my next TODO item. I've something drafted and have made a couple of
> >assumptions. Could you tell me if these would fit your needs?
> >
> >**NOTE:** I'm using the term 'lab
On 22 Mar 08:37, Wolfram Sang wrote:
>
> > > Patches applied using pwclient will always use the first name that has
> > > been seen for a particular email address. While this is usually fine, It
> > > actually causes issues for people changing name without changing email
> > > addresses or people
> > Patches applied using pwclient will always use the first name that has
> > been seen for a particular email address. While this is usually fine, It
> > actually causes issues for people changing name without changing email
> > addresses or people changing the capitalization of their name (less
