From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2307 invoked by alias); 14 May 2006 06:57:52 -0000 Received: (qmail 2298 invoked by uid 22791); 14 May 2006 06:57:52 -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; Sun, 14 May 2006 06:57:36 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 9A24C48CC4F; Sun, 14 May 2006 02:57:34 -0400 (EDT) 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 11521-01; Sun, 14 May 2006 02:57:34 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 44B5F48CBB1; Sun, 14 May 2006 02:57:34 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id A710247E7F; Sat, 13 May 2006 23:57:32 -0700 (PDT) Date: Sun, 14 May 2006 10:41:00 -0000 From: Joel Brobecker To: Nick Roberts Cc: gdb@sources.redhat.com Subject: Re: GDB 6.5 branch on Sun May 14th Message-ID: <20060514065732.GC6718@adacore.com> References: <20060514050107.GA6718@adacore.com> <17510.49478.586246.146949@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17510.49478.586246.146949@farnswood.snap.net.nz> User-Agent: Mutt/1.4i 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-05/txt/msg00189.txt.bz2 > > Now that the last couple of patches I thought were important enough to > > delay 6.5 are in, I was thinking that maybe tomorrow would be a good > > day to use as the start of the 6.5 branch. Any better suggestion? > > Could I sneak in the change to -var-set-format that I submitted earlier? > (reproduced below). There must be a chance that Emacs 22 will be released > before the GDB release after 6.5, and then I'll be up and running. I am not opposed, but remember that you can always port this change to the branch if the patch is deemed safe enough but is committed too late. -- Joel