Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Ben Elliston <bje@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] target.c patch
Date: Fri, 26 Apr 2002 15:03:00 -0000	[thread overview]
Message-ID: <3CC9CEC5.2050009@cygnus.com> (raw)
In-Reply-To: <3CC9C5B0.D07E008E@redhat.com>

> Ben Elliston wrote:
> 
>> 
>> I noticed a comment about a "trust-readonly" option, yet it is called
>> "trust-readonly-sections" -- fixed.  Okay to commit?
>> 
>> Ben
> 
> 
> Yes, please do.  Thanks.

This brings up a general wierdness.  You're mentioned in sim/MAINTAINERS 
but not gdb/MAINTAINERS.

I think I might tweak things so that everyone is mentioned under write 
after approval so that there is no confusion - hopefully people can cope 
with multiple roles :-)

enjoy,
Andrew


>> 2002-04-26  Ben Elliston  <bje@redhat.com>
>> 
>> * target.c (do_xfer_memory): Correct reference to the new option
>> "trust-readonly-sections".
>> 
>> Index: target.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/target.c,v
>> retrieving revision 1.33
>> diff -u -r1.33 target.c
>> --- target.c    1 Feb 2002 01:01:21 -0000       1.33
>> +++ target.c    26 Apr 2002 21:07:52 -0000
>> @@ -861,9 +861,9 @@
>> 
>> if (!write && trust_readonly)
>> {
>> -      /* User-settable option, "trust-readonly".  If true, then
>> -        memory from any SEC_READONLY bfd section may be read
>> -        directly from the bfd file. */
>> +      /* User-settable option, "trust-readonly-sections".  If true,
>> +         then memory from any SEC_READONLY bfd section may be read
>> +         directly from the bfd file. */
>> 
>> struct section_table *secp;



      reply	other threads:[~2002-04-26 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 14:09 Ben Elliston
2002-04-26 14:37 ` Michael Snyder
2002-04-26 15:03   ` Andrew Cagney [this message]

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=3CC9CEC5.2050009@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=bje@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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