(I have put these directions at http://www.dberlin.org/~dberlin/patchdirections.html)
After much discussion on IRC. I've set up a simple patch queue for tracking patches at http://www.dberlin.org/cgi-bin/patches.py The data in there is real, those are patches that need to be reviewed, along with the correct submit dates. The tracking is *mostly* automatic. If you want a patch tracked, please have a line in your email to gcc-patches that consists of solely :ADDPATCH <maintenance area>: It ignores other lines, so you can put this at the top, the middle, or wherever. It just has to be somewhere in the email on a line by itself Example:" This is patch blah blah blah :ADDPATCH SSA: Thanks, Dan " or " :ADDPATCH SSA: This is patch blah blah blah Thanks, Dan " but *not* " This is patch blah blah blah :ADDPATCH SSA: Thanks, Dan " It should show up in the patch tracker soon afterwards (i'm currently running the scanner manually every hour or so). If you have forgotten to do this, you can add a patch to the tracker manually using the add link at the bottom of the tracker. Patches added manually must be removed manually too If you review a patch by replying from your mailer, simply reply to the email that had the ADDPATCH line in it, and include a line: :REVIEWMAIL: It will figure out which patch you were reviewing (by the in-reply-to column) and remove it from the queue list. If you are replying to something out of the archives, please put :REVIEWURL <mailing list archive url>: If you are just randomly reviewing patches you found on the tracker, and are too lazy to post the url, simply include: :REVIEWID <patch id>: and it will mark the patch as reviewed. You can also manually remove patches through the remove link. I may disable this feature if it is abused (or restrict it's access). The tracker is quite simple for now, and just lists the patches along with a submit date and archive url, and color codes the dates by how long they have been outstanding. More may come later (pinging, whatever):)
