From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20127 invoked by alias); 6 Jan 2015 16:38:18 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 20117 invoked by uid 89); 6 Jan 2015 16:38:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 06 Jan 2015 16:38:11 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 387C2116484; Tue, 6 Jan 2015 11:38:09 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ILYIzS9xDA5B; Tue, 6 Jan 2015 11:38:09 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id BD665116483; Tue, 6 Jan 2015 11:38:08 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 81A1F4100E; Tue, 6 Jan 2015 20:38:04 +0400 (RET) Date: Tue, 06 Jan 2015 16:38:00 -0000 From: Joel Brobecker To: Steve Ellcey Cc: gdb-patches@sourceware.org Subject: Re: GDB 7.9 branching - 2 weeks to go (Mon, Jan 12th)! Message-ID: <20150106163804.GK5445@adacore.com> References: <20141230071500.GF2123@adacore.com> <1420560568.15691.25.camel@ubuntu-sellcey> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1420560568.15691.25.camel@ubuntu-sellcey> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2015-01/txt/msg00081.txt.bz2 > I think PR gdb/17718 should be considered a blocking bug because it > breaks the builds on some systems (depending on what version of GCC is > used to build). It should not break the build, actually, because releases are configured to make --disable-werror the default. The change is performed as soon as the branch is cut. So we should be OK. -- Joel