From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28924 invoked by alias); 3 Sep 2012 07:46:42 -0000 Received: (qmail 28915 invoked by uid 22791); 3 Sep 2012 07:46:39 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from mel.act-europe.fr (HELO mel.act-europe.fr) (194.98.77.210) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Sep 2012 07:46:26 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 0745F29005B; Mon, 3 Sep 2012 09:46:35 +0200 (CEST) Received: from mel.act-europe.fr ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dU0Dvqg2a81T; Mon, 3 Sep 2012 09:46:34 +0200 (CEST) Received: from ulanbator.act-europe.fr (ulanbator.act-europe.fr [10.10.1.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mel.act-europe.fr (Postfix) with ESMTP id E9C36290016; Mon, 3 Sep 2012 09:46:34 +0200 (CEST) Subject: Re: Release 2.23: Ping Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Tristan Gingold In-Reply-To: Date: Mon, 03 Sep 2012 07:46:00 -0000 Cc: binutils@sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: <27287C89-8E9D-4C52-9D78-F3AA7700B902@adacore.com> References: To: Jeff Sheldon X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00017.txt.bz2 On Aug 31, 2012, at 10:56 PM, Jeff Sheldon wrote: > On Fri, Aug 31, 2012 at 10:34 AM, Tristan Gingold wrote: >> as far as I understand, aarch64 was committed in the 2.23 branch. I'd l= ike to thanks for doing this timely. >>=20 >> Is there any patch that need to be in the 2.23 release ? Please, reply = quickly as I'd like to do the release soon. >=20 > If commits are made to master after 2.3 is released, will they be > allowed to go into 2.3.1 or is that reserved strictly for fixes (while > new commits work towards 2.4)? Note that the version is 2.23 Backport commits are reserved for fixes, but there are always some exceptio= ns... Tristan.