From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6128 invoked by alias); 9 Jun 2006 14:28:20 -0000 Received: (qmail 6120 invoked by uid 22791); 9 Jun 2006 14:28:20 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 09 Jun 2006 14:28:18 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FohyC-0007Yp-F7 for gdb@sourceware.org; Fri, 09 Jun 2006 10:28:16 -0400 Date: Fri, 09 Jun 2006 17:00:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Patch tracker now available Message-ID: <20060609142816.GA28863@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <20060330001459.GA13813@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060330001459.GA13813@nevyn.them.org> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00064.txt.bz2 On Wed, Mar 29, 2006 at 07:14:59PM -0500, Daniel Jacobowitz wrote: > Daniel Berlin offered in February to set up a patch queue. It's some > custom software that he wrote for GCC, after two consecutive GCC Summits > in which people agreed that they wanted some automated way to keep track of > patches, but no one came up with anything that seemed usable. Everyone who responded liked this idea, so I've set one up. It was a pile of work to get running, so I hope it's useful :-) It's here: http://gdb.false.org/patches It is certainly not mandatory for patch submitters or reviewers. It has both an email interface (it scans the web archives hourly looking for commands) and a web interface; if I find it useful I can add patches to it even when they weren't posted with appropriate tags. There's some instructions on how to use it by email up top of the list. If you have any suggestions or problems, please let me know. If it proves useful, we can make it more prominent, for instance by a link from the GDB web site. In the mean time, I encourage patch submitters to use it. There is an associated rant, which is that I'd really appreciate more help in reviewing submitted patches. I hope that adding tracking will make it easier to see what needs review. -- Daniel Jacobowitz CodeSourcery