From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: NEWS entries for 6.1.1 dwarf changes?
Date: Fri, 11 Jun 2004 15:17:00 -0000 [thread overview]
Message-ID: <40C9CD11.1000702@gnu.org> (raw)
In-Reply-To: <200406111421.i5BELAr1001522@elgar.kettenis.dyndns.org>
> Date: Fri, 11 Jun 2004 00:34:03 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> Hello,
>
> These 6.1.1 changes need a NEWS entry, anyone?
>
> 2004-05-01 Mark Kettenis <kettenis@gnu.org>
>
> * 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
next prev parent reply other threads:[~2004-06-11 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 4:34 Andrew Cagney
2004-06-11 14:21 ` Mark Kettenis
2004-06-11 15:17 ` Andrew Cagney [this message]
2004-06-11 15:18 ` Andrew Cagney
2004-06-11 17:07 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40C9CD11.1000702@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox