This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Tracking patch pings
- From: Andreas Jaeger <aj at suse dot com>
- To: libc-alpha at sourceware dot org
- Date: Thu, 16 May 2013 09:30:01 +0200
- Subject: Re: Tracking patch pings
- References: <Pine dot LNX dot 4 dot 64 dot 1305152117141 dot 21321 at digraph dot polyomino dot org dot uk>
On 05/15/2013 11:20 PM, 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.)
My impression is that we have a couple of patches that get pinged but
it's not such a large number that we need an automated tool and
something low tech like a wiki page would be a good start - and it would
tell us more about the size of the problem.
I'm not objecting to a tool like patchwork - my suggestion is to start
with a low-tech solution and see whether that helps,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126