From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 810 invoked by alias); 30 Mar 2006 00:15:03 -0000 Received: (qmail 801 invoked by uid 22791); 30 Mar 2006 00:15:02 -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; Thu, 30 Mar 2006 00:15:01 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FOkoV-0003cm-Vy for gdb@sourceware.org; Wed, 29 Mar 2006 19:15:00 -0500 Date: Thu, 30 Mar 2006 01:14:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Using a patch queue? Message-ID: <20060330001459.GA13813@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.8i 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-03/txt/msg00210.txt.bz2 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. Here's the GCC one: http://www.dberlin.org/patches/ http://dberlin.org/patchdirections.html I've never used it except to play with it, but a lot of GCC contributors do, as you can see. I think that's a pretty compelling point in its favor, since they have a similar workflow to ours. The patch tracker follows the list (via the web archives, I think) and collects annotated messages. You're under no obligation to annotate your messages; anyone can manually add a URL to the patch tracker via the web interface. I believe the first review response removes the patch from the queue; we might want to save :REVIEWMAIL: for final approval/rejection. Or it might be useful enough just to track patches which have never been looked at, which happens quite a lot. I wouldn't mind having a better tool than my inbox to track down what needs looking at; I don't have enough time to review everything that needs reviewing as it is. Anyone else have an opinion? -- Daniel Jacobowitz CodeSourcery