From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2715 invoked by alias); 11 Jun 2004 15:17:50 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2695 invoked from network); 11 Jun 2004 15:17:48 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 11 Jun 2004 15:17:48 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5BFHmi7004876 for ; Fri, 11 Jun 2004 11:17:48 -0400 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5BFHl005362; Fri, 11 Jun 2004 11:17:48 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id BE63E2B9D; Fri, 11 Jun 2004 11:17:37 -0400 (EDT) Message-ID: <40C9CD11.1000702@gnu.org> Date: Fri, 11 Jun 2004 15:17:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Mark Kettenis Cc: gdb-patches@sources.redhat.com Subject: Re: NEWS entries for 6.1.1 dwarf changes? References: <40C9363B.5040108@gnu.org> <200406111421.i5BELAr1001522@elgar.kettenis.dyndns.org> In-Reply-To: <200406111421.i5BELAr1001522@elgar.kettenis.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00261.txt.bz2 > Date: Fri, 11 Jun 2004 00:34:03 -0400 > From: Andrew Cagney > > Hello, > > These 6.1.1 changes need a NEWS entry, anyone? > > 2004-05-01 Mark Kettenis > > * dwarf2-frame.c (read_encoded_value): Handle DW_EH_PE_funcrel > encondings. Fixes PR gdb/1628. > > Andrew > > Would that be really useful? This stuff is mentioned in the > ChangeLog. Yes. The NEWS entries, included in the 6.1.1 announcement, tell the user know what was fixed (not how). Conversely, the ChangeLog (as it should) tells us what was changed, not why. Andrew > Oh well, I don't want to hold up the release, so here's > some blurb about the change shown above. > Committed to the branch, > > Mark