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: Allan McRae <allan at archlinux dot org>
- Cc: David Miller <davem at davemloft dot net>, <vapier at gentoo dot org>, <libc-alpha at sourceware dot org>
- Date: Wed, 15 May 2013 22:40:44 +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> <Pine dot LNX dot 4 dot 64 dot 1305152211130 dot 21321 at digraph dot polyomino dot org dot uk> <51940C5D dot 9070707 at archlinux dot org>
On Thu, 16 May 2013, Allan McRae wrote:
> From what I have seen, it considers the new version of the patch as a
> comment and updates the version of the patch it is tracking. I can not
> remember if it changes its status back to New. Of course, that is
> provided the new patch is sent in a reply and not a new thread.
Changing it back to New would be a very good idea to avoid patches getting
lost (given the much of the point of such a tracker is to avoid patches
getting lost).
> It is all very manual. However, it does allow me to keep track of all
> the patches I have not reviewed, which has been good for a small
> project. It would require somebody to manage it if used in a bigger
> project such as glibc or a concerted effort by reviewers/committers to
> keep it updated.
I'm happy for someone to set it up to track libc-alpha and libc-ports -
but for it to be particularly useful, I think we need someone who is going
to keep it updated like that, as patches get reviewed and committed.
--
Joseph S. Myers
joseph@codesourcery.com