From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] constify symfile.h section_offsets, section_addr_info
Date: Mon, 06 May 2013 18:37:00 -0000 [thread overview]
Message-ID: <87d2t4ymxl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yjt2sj20capi.fsf@ruffy2.mtv.corp.google.com> (Doug Evans's message of "Mon, 06 May 2013 09:52:25 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> While researching the bfd section count bug,
Doug> I found some things a bit confusing: some parameters seemed to be just for
Doug> input but weren't marked with const (thus I had to dig deeper than I might
Doug> otherwise have had to).
Doug> Thus I've gone through and constified a few things.
Doug> I will commit this in a few days if there are no objections.
It looks good to me.
Thanks for doing this.
Tom
next prev parent reply other threads:[~2013-05-06 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 16:52 Doug Evans
2013-05-06 18:37 ` Tom Tromey [this message]
2013-05-06 19:17 ` Doug Evans
2013-05-06 19:37 ` Tom Tromey
2013-05-06 19:40 ` Doug Evans
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=87d2t4ymxl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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