From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11225 invoked by alias); 3 Sep 2009 21:35:41 -0000 Received: (qmail 11212 invoked by uid 22791); 3 Sep 2009 21:35:41 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Sep 2009 21:35:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 291CF2BAB4A; Thu, 3 Sep 2009 17:35:33 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CQnQPxEIC36C; Thu, 3 Sep 2009 17:35:33 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id DBC152BAB37; Thu, 3 Sep 2009 17:35:32 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id D7F47F589A; Thu, 3 Sep 2009 14:35:22 -0700 (PDT) Date: Thu, 03 Sep 2009 21:35:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: Eli Zaretskii , gdb@sourceware.org Subject: Re: [gdb-7.0 release] 2009-09-02 status and proposed plan Message-ID: <20090903213522.GG4379@adacore.com> References: <20090902164425.GR4379@adacore.com> <83skf490r6.fsf@gnu.org> <20090903192746.GD4379@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00056.txt.bz2 > I am unhappy with the facts of the situation: we've had a nice new > feature, rewritten several times, pending since April. I know both from > personal experience, and from talking to contributors, that this sort of > thing is very demoralizing, and consequently hurts GDB. I definitely share your feeling. We should try to find ways to reduce the risk of this happening again, and in the meantime let's try to be responsive to his patches. Have the patches been sitting unreviewed since April? -- Joel