From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27742 invoked by alias); 21 Apr 2009 15:52:30 -0000 Received: (qmail 27681 invoked by uid 22791); 21 Apr 2009 15:52:29 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 21 Apr 2009 15:52:19 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3LFq8Sc008526; Tue, 21 Apr 2009 11:52:08 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3LFq7dX032160; Tue, 21 Apr 2009 11:52:07 -0400 Received: from opsy.redhat.com (vpn-14-116.rdu.redhat.com [10.11.14.116]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3LFq5C2015245; Tue, 21 Apr 2009 11:52:06 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 7509C37829A; Tue, 21 Apr 2009 09:52:04 -0600 (MDT) To: nickrob@snap.net.nz (Nick Roberts) Cc: Thiago Jung Bauermann , gdb ml Subject: Re: GDB and the Google Summer of Code References: <1240266843.17964.16.camel@localhost.localdomain> <18925.33674.230789.972718@totara.tehura.co.nz> From: Tom Tromey Reply-To: tromey@redhat.com Date: Tue, 21 Apr 2009 16:26:00 -0000 In-Reply-To: <18925.33674.230789.972718@totara.tehura.co.nz> (Nick Roberts's message of "Tue\, 21 Apr 2009 20\:27\:54 +1200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-04/txt/msg00173.txt.bz2 >>>>> "Nick" == Nick Roberts writes: Nick> Although Tom Tromey was adamant on the GNU summer-of-code Nick> mailing list that this was not a GDB project, I hope it can Nick> enjoy similar support from this mailing list. I'll adamantly support it ;) Nick> Also that any patches for GDB that we may have could be reviewed Nick> and (possibly) approved within the timescale of the project Nick> (about eight weeks). I can only speak for myself -- I'll try my best. Make sure he knows to ping patches after a week. I've noticed a few gdb patches that have fallen through the cracks for lack of pinging. Tom