From: Daniel Jacobowitz <drow@mvista.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Correct double negative in gdbint.texinfo
Date: Wed, 14 May 2003 20:14:00 -0000 [thread overview]
Message-ID: <20030514201445.GA8463@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0305141118050.25620@knuth.amplepower.com>
On Wed, May 14, 2003 at 11:26:07AM -0700, Theodore A. Roth wrote:
> Hi,
>
> This patch is strictly a grammar change.
>
> I'm not sure if "need not do anything" or "need do nothing" sounds
> better though.
>
> Ok to commit?
OK as an obvious fix, thanks. I think I prefer "need not do anything".
>
> Ted Roth
> 2003-05-14 Theodore A. Roth <troth@openavr.org>
>
> * doc/gdbint.texinfo: Correct a double negative.
>
> Index: doc/gdbint.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.144
> diff -u -r1.144 gdbint.texinfo
> --- doc/gdbint.texinfo 5 May 2003 17:56:57 -0000 1.144
> +++ doc/gdbint.texinfo 14 May 2003 17:55:56 -0000
> @@ -288,7 +288,7 @@
> breakpoints somehow; for instance, a ROM monitor may do its own
> software breakpoints. So although these are not literally ``hardware
> breakpoints'', from @value{GDBN}'s point of view they work the same;
> -@value{GDBN} need not do nothing more than set the breakpoint and wait
> +@value{GDBN} need not do anything more than set the breakpoint and wait
> for something to happen.
>
> Since they depend on hardware resources, hardware breakpoints may be
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-14 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 18:22 Theodore A. Roth
2003-05-14 20:14 ` Daniel Jacobowitz [this message]
2003-05-14 20:32 ` Theodore A. Roth
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=20030514201445.GA8463@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=troth@openavr.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