Re: Tracking patch pings

["Joseph S. Myers" <joseph at codesourcery dot com>]

On Wed, 15 May 2013, Mike Frysinger wrote:

> On Wednesday 15 May 2013 17:20:10 Joseph S. Myers wrote:
> > To raise more visibly something I mentioned in another thread:
> > 
> > Should we have some system for tracking patches that are pending review,
> > especially those that have been pinged?  For example, there could be a
> > list on the wiki page for the current release cycle of patches believed to
> > be ready for review and the contribution checklist could say to add your
> > patch there when pinging it.  (Ideally we'd have people who specifically
> > try to keep a lookout for unreviewed patches and add them to the list
> > after a week even if not pinged.)
> 
> or use patchwork ?
> http://patchwork.ozlabs.org/
> 
> looks like they're handling gcc-patches already.  and they have the 
> infrastructure.  all we have to do is ask them to turn it on and see how it 
> goes ? :)

The GCC list has thousands of patches in it.  To be useful someone would 
need to remove non-patches and reviewed patches promptly, to the extent it 
can't do that automatically.  If someone's interested in doing that, sure, 
setting it up to monitor libc-alpha and libc-ports makes sense.  I guess 
then people who know about older patches pending review should get them 
reposted to enter them in the system.

(It doesn't seem clear from the documentation ... I assume patchwork will 
do sensible things if e.g. a patch is marked reviewed and then a 
subsequent revision of that patch is posted and so needs to be visible as 
needing review, or if a thread ends up containing discussions of multiple 
different patches.)

-- 
Joseph S. Myers
joseph@codesourcery.com