From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20344 invoked by alias); 10 Jun 2010 20:12:13 -0000 Received: (qmail 20294 invoked by uid 22791); 10 Jun 2010 20:12:03 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_20,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-ww0-f47.google.com (HELO mail-ww0-f47.google.com) (74.125.82.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Jun 2010 20:11:59 +0000 Received: by wwb17 with SMTP id 17so236915wwb.20 for ; Thu, 10 Jun 2010 13:11:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.152.196 with SMTP id h4mr784889wbw.61.1276200337828; Thu, 10 Jun 2010 13:05:37 -0700 (PDT) Received: by 10.216.229.169 with HTTP; Thu, 10 Jun 2010 13:05:37 -0700 (PDT) In-Reply-To: References: <201006071901.03000.ebotcazou@adacore.com> <4C0D4A26.6080703@oracle.com> <4C0D5792.8090005@oracle.com> <4C0D62F5.908@oracle.com> Date: Thu, 10 Jun 2010 20:26:00 -0000 Message-ID: Subject: Re: Patch pinging From: Quentin Neill To: gcc@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-06/txt/msg00411.txt.bz2 On Tue, Jun 8, 2010 at 6:30 AM, Jonathan Wakely wrote: > On 7 June 2010 22:43, Ian Lance Taylor wrote: >> >> The patch tracker (http://gcc.gnu.org/wiki/GCC_Patch_Tracking) is not >> currently operating. >> >> Would anybody like to volunteer to get it working again? > > I'm not volunteering, but I might look into it one day.... > > If dberlin doesn't still have the code, it shouldn't be too hard... > > ... a script which periodically crawls the gcc-patches archive might suffice... I have a python script which crawls, caches, and parses the gcc-cvs (and binutils-cvs) email archive pages. I wrote it to help another script that correlates patch revisions in a branch (where the Changelog refers to revisions on the trunk) back to the useful Changelog entries in the trunk. I could submit that to contrib, it could be modified to scrape most of the information above into a single monthly report. Any interest? -- Quentin Neill