From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18274 invoked by alias); 6 May 2013 18:19:25 -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 18265 invoked by uid 89); 6 May 2013 18:19:24 -0000 X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 06 May 2013 18:19:24 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r46IJJ0v019943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 May 2013 14:19:19 -0400 Received: from barimba (ovpn-113-163.phx2.redhat.com [10.3.113.163]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r46IJHaO020877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 6 May 2013 14:19:17 -0400 From: Tom Tromey To: Eli Zaretskii Cc: Joel Brobecker , jan.kratochvil@redhat.com, gdb-patches@sourceware.org Subject: Re: [ANNOUNCEMENT] GDB 7.6 released! References: <83k3nptk18.fsf@gnu.org> <837gjotnc9.fsf@gnu.org> <20130428073805.GU3525@adacore.com> <20130505194406.GA15079@host2.jankratochvil.net> <20130506103203.GC5278@adacore.com> <83ehdkf5ei.fsf@gnu.org> Date: Mon, 06 May 2013 18:19:00 -0000 In-Reply-To: <83ehdkf5ei.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 May 2013 19:18:45 +0300") Message-ID: <87k3ncynrv.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-05/txt/msg00132.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> So is it OK to include exceptions.h in utils.h? Sure. I would zap the "enum errors;" line at the same time. It doesn't add anything. Tom