RFC/slightly offtopic: Automatic patchwork status updates

RFC/slightly offtopic: Automatic patchwork status updates

[Jeremy Kerr]

Hi all,

For some time now, we've been running patchwork on the linuxppc and 
cbe-oss-dev lists. For those who haven't seen it, it collects and 
tracks patches posted to the lists, and shows them here:

  http://patchwork.ozlabs.org/linuxppc
and
  http://patchwork.ozlabs.org/cbe-oss-dev

However, the patch 'state' (eg, accepted, rejected, debug only, changes 
requested) doesn't get updated very often, as it can be an unnecessary 
burden on the maintainers.

All this information is available from the actual upstream tree itself, 
so essentially patchwork *should* be able to just mirror the state.

So, I'd like to get a bit of discussion on how we can get this (or at 
least most of it!) done automatically. For instance, can we come up 
with a scheme that can detect if a patch has made it into paulus' tree 
with some reasonable error rate?

If we can get something sketched up, I'll implement & integrate into 
patchwork. Seeing as this is an own-time project for me though, there 
will probably be a little latency in the process ;)

Cheers,


Jeremy

PS. do we need to create a separate patchwork list and move discussion 
there?

Re: RFC/slightly offtopic: Automatic patchwork status updates

[Michael Neuling]

> For some time now, we've been running patchwork on the linuxppc and 
> cbe-oss-dev lists. For those who haven't seen it, it collects and 
> tracks patches posted to the lists, and shows them here:
> 
>   http://patchwork.ozlabs.org/linuxppc
> and
>   http://patchwork.ozlabs.org/cbe-oss-dev
> 
> However, the patch 'state' (eg, accepted, rejected, debug only, changes 
> requested) doesn't get updated very often, as it can be an unnecessary 
> burden on the maintainers.
> 
> All this information is available from the actual upstream tree itself, 
> so essentially patchwork *should* be able to just mirror the state.

Personally, I use the git web server on kernel.org to see if my patches
are in a particular tree.  I have a bookmark something like this:

http://git.kernel.org/git/?p=linux/kernel/git/paulus/powerpc.git&a=search&h=HEAD&s=Jeremy+Kerr

This may not solve all the problems you are trying to solve with
patchworks though.  

Mikey