From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11953 invoked by alias); 25 Apr 2002 16:19:04 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 11692 invoked from network); 25 Apr 2002 16:18:32 -0000 Received: from unknown (HELO mms2.broadcom.com) (63.70.210.59) by sources.redhat.com with SMTP; 25 Apr 2002 16:18:32 -0000 Received: from 63.70.210.1 by mms2.broadcom.com with ESMTP (Broadcom MMS-2 SMTP Relay (MMS v4.7)); Thu, 25 Apr 2002 09:16:55 -0700 X-Server-Uuid: 2a12fa22-b688-11d4-a6a1-00508bfc9626 Received: from dt-sj3-118.sj.broadcom.com (dt-sj3-118 [10.21.64.118]) by mail-sj1-5.sj.broadcom.com (8.12.2/8.12.2) with ESMTP id g3PGIV1S003147; Thu, 25 Apr 2002 09:18:31 -0700 (PDT) Received: (from cgd@localhost) by dt-sj3-118.sj.broadcom.com ( 8.9.1/SJ8.9.1) id JAA00782; Thu, 25 Apr 2002 09:18:30 -0700 (PDT) To: ac131313@cygnus.com cc: "David S. Miller" , kevinb@redhat.com, shebs@apple.com, drow@mvista.com, gdb-patches@sources.redhat.com Subject: Re: which patches to review References: <20020424.103856.00478620.davem@redhat.com> <1020424191644.ZM15056@localhost.localdomain> <20020424.121543.128593116.davem@redhat.com> <3CC80CDF.6030409@cygnus.com> From: cgd@broadcom.com Date: Thu, 25 Apr 2002 09:19:00 -0000 In-Reply-To: ac131313@cygnus.com's message of "Thu, 25 Apr 2002 14:04:30 +0000 (UTC)" Message-ID: MIME-Version: 1.0 X-WSS-ID: 10D6F47D4013-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01020.txt.bz2 At Thu, 25 Apr 2002 14:04:30 +0000 (UTC), "Andrew Cagney" wrote: > David, to (possibly re-iterate) some previous suggestions: > > > If you post a new patch, start a new thread. > > If you superseed a patch, clearly withdraw the old patch. > > This makes life easier for everyone and is accepted pratice on this list. My personal practice, which i've found helpful in the past, is to keep a list of patches i've submitted, keep track of their status, and occasionally send a ping msg containing the list of unreviewed patches that have gone "too long" w/o approval or rejection. Like it or not, even in the best circumstances things _do_ get lost, dropped, overlooked, or otherwise ignored occasionally. That's especially true when volunteers are doing the reviewing, and the volunteers are busy. I've found that it also helps me keep track of my own outstanding patches when _I_ get really busy and distracted for a month at a time... 8-) (my personal cutoff for 'too long' tends to be '2 weeks to a month, or whenever after a longer period i remember to look at my outstanding patches page.' 8-) chris