From: Jim Blandy <jimb@redhat.com>
To: David Lecomber <david@streamline-computing.com>
Cc: Daniel Jacobowitz <drow@false.org>,
patches <gdb-patches@sources.redhat.com>
Subject: Re: Dwarf2 Producer info
Date: Wed, 28 Jul 2004 19:05:00 -0000 [thread overview]
Message-ID: <vt2fz7cdkdc.fsf@zenia.home> (raw)
In-Reply-To: <1090394885.21483.134.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com>
David Lecomber <david@streamline-computing.com> writes:
> Fine by me -- in fact, even the null setting isn't needed now I've found
> the bit that ensures the cu is cleared during allocation (do you
> agree?).
Looks fine --- but you need a ChangeLog entry for the change to
'struct dwarf2_cu', as well as the change to read_file_scope.
With that change, this is okay.
next prev parent reply other threads:[~2004-07-28 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 22:14 David Lecomber
2004-07-20 23:18 ` Daniel Jacobowitz
2004-07-20 23:40 ` David Lecomber
2004-07-21 0:09 ` Daniel Jacobowitz
2004-07-21 7:12 ` David Lecomber
2004-07-21 13:25 ` Daniel Jacobowitz
2004-07-28 19:05 ` Jim Blandy [this message]
2004-07-26 20:55 ` [RFA] Dwarf2 Producer info (dwarf2read.c) David Lecomber
2004-07-29 10:28 ` David Lecomber
2004-07-29 19:25 ` Jim Blandy
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=vt2fz7cdkdc.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=david@streamline-computing.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/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