From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28332 invoked by alias); 17 Nov 2006 17:35:19 -0000 Received: (qmail 28324 invoked by uid 22791); 17 Nov 2006 17:35:18 -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, 17 Nov 2006 17:35:07 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Gl7cE-0001Qa-VG; Fri, 17 Nov 2006 12:35:03 -0500 Date: Fri, 17 Nov 2006 17:35:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: GDB 6.6 branch cut off date: 2006-11-15 ? Message-ID: <20061117173502.GB5388@nevyn.them.org> Mail-Followup-To: Joel Brobecker , gdb@sourceware.org References: <20061117172904.GD3365@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061117172904.GD3365@adacore.com> User-Agent: Mutt/1.5.13 (2006-08-11) 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-11/txt/msg00123.txt.bz2 On Fri, Nov 17, 2006 at 09:29:04AM -0800, Joel Brobecker wrote: > Hello, > > I am trying to decide at which point in time should we start the > GDB 6.6 branch. I propose 2006-11-15, which is right after the > Xtensa port was checked in. We will be missing: > > 2006-11-16 Maxim Grigoriev > > * MAINTAINERS (Responsible Maintainers): Add myself for Xtensa. > (Write After Approval): Add myself. > > 2006-11-16 Daniel Jacobowitz > > * remote.c (PACKET_QPassSignals): New. > (last_pass_packet, remote_pass_signals): New. > (remote_protocol_features): Add QPassSignals. > (remote_query_supported): Correct an infinite loop. > (remote_open_1): Reset last_pass_packet. > (remote_resume): Call remote_pass_signals. > (_initialize_remote): Register "set remote pass-signals". > > If I cut the branch at the date I planned, I will definitely port > the change to MAINTAINERS. How about the second? I'd rather have it included, along with the NEWS entry for it which I'll commit in a second, since we just got a bug report that it should fix. But I won't be heartbroken if it isn't. I'll likely add it to the Debian packaged version though. > I will try to cut the branch this week-end, and start the testing. > Target release date: One month after that, which would be around > December 18th. This sounds excellent. Should I assume that the branch will be dated at some point before today, then? -- Daniel Jacobowitz CodeSourcery