From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32135 invoked by alias); 17 Nov 2006 17:40:27 -0000 Received: (qmail 32125 invoked by uid 22791); 17 Nov 2006 17:40:26 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Nov 2006 17:40:19 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 0159848CC0C for ; Fri, 17 Nov 2006 12:40:18 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13336-01-4 for ; Fri, 17 Nov 2006 12:40:17 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id B271748CBC5 for ; Fri, 17 Nov 2006 12:40:17 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 8616834C099; Fri, 17 Nov 2006 09:40:35 -0800 (PST) Date: Fri, 17 Nov 2006 17:40:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: Re: GDB 6.6 branch cut off date: 2006-11-15 ? Message-ID: <20061117174035.GE3365@adacore.com> References: <20061117172904.GD3365@adacore.com> <20061117173502.GB5388@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061117173502.GB5388@nevyn.them.org> User-Agent: Mutt/1.4.2.2i 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/msg00124.txt.bz2 > > 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. No problem, I'll make sure it's part of the branch. > > 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? Yes. I chose the 15th because there was little activity. In all likeliness, unless someone makes a better suggestion, I will date the branch on the 15th, and then port the 3 patches to the branch (remote.c, MAINTAINERS, and NEWS). -- Joel