This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Tracking patch pings
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: David Miller <davem at davemloft dot net>
- Cc: <vapier at gentoo dot org>, <libc-alpha at sourceware dot org>
- Date: Wed, 15 May 2013 22:16:58 +0000
- 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> <201305151728 dot 04922 dot vapier at gentoo dot org> <Pine dot LNX dot 4 dot 64 dot 1305152134260 dot 21321 at digraph dot polyomino dot org dot uk> <20130515 dot 145315 dot 1427780454791394565 dot davem at davemloft dot net>
On Wed, 15 May 2013, David Miller wrote:
> > 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.
>
> Patchwork, as the web site several of us have given you the URL to
> explains, knows what a patch looks like and does not track
> non-patches.
The website appears to have very little information. The "docs" link at
the top of <http://jk.ozlabs.org/projects/patchwork/> appears to have
nothing to do with patchwork at all. There appears to be little
documentation in the patchwork source distribution either. I can't tell
from either of those whether a patch sent in the thread discussing a
previous patch revision will be considered by patchwork as something new,
or as a comment on the previous version (and so not very visible if the
previous version has been marked as reviewed), for example.
But I don't see anything indicating that it will automatically detect
whether patches are reviewed, meaning that for it to be more useful for
glibc than the list of thousands of patches for GCC, someone needs to be
maintaining the list of patches in the patchwork instance - marking
reviewed patches as such - so that if we want to clear the review backlog
as we approach a release freeze, patchwork does actually show the backlog
contents and not a huge pile of patches 90% of which were reviewed long
ago.
--
Joseph S. Myers
joseph@codesourcery.com