"Segher Boessenkool" <seg...@kernel.crashing.org> writes:

> Jeremy has set up a Patchwork instance for us at
>
>    http://patchwork.ozlabs.org/project/gcc/list/ .
>
> It is feeding from gcc-patches; the plan is to make it
> automatically recognise what patches went into the tree,
> probably by snooping the gcc-cvs list.
>
> You can also manually change patch status, if you're an
> admin; who is admin currently has to be configured manually,
> plan is to make everyone with an email @gcc.gnu.org admin
> automatically.  In the meantime, if you want to play with
> it, tell me and I'll get you added.
>
> There aren't many patches in the system yet, so we'll need
> to let it run for a few weeks at least for it to prove its
> worth.
>
> Any feedback is very welcome.  Go play with it :-)


This is quite interesting, thanks for setting it up.


I can see already that to be useful for gcc today it will need some
curating.  E.g., http://patchwork.ozlabs.org/patch/54974/ is both 1)
committed; 2) on a branch.  This one
http://patchwork.ozlabs.org/patch/54958/ is committed to trunk.  Are
there ways that we can adjust our e-mail messages to make this work
better?

Ian

Reply via email to