Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "John R. Moore" <jmoore@redhat.com>
To: gdb-patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] tiny spelling corrections in gdbint.text
Date: Tue, 17 Jul 2001 13:57:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.31.0107171356440.25568-100000@cse.cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.31.0107171350250.25568-100000@cse.cygnus.com>

Oops, change the change log to say:

	* gdbint.texinfo: Fixed three misspellings.

-------------------------------

On Tue, 17 Jul 2001, John R. Moore wrote:

>
> 2001-07-17  John R. Moore  <jmoore@redhat.com>
>
> 	* gdbint.texinfo: fixed three misspelling words.
>
> Index: gdb/doc/gdbint.texinfo
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.173
> diff -p -u -r1.173 gdbint.texinfo
> --- gdb/doc/gdbint.texinfo	2001/07/13 23:56:09	1.173
> +++ gdb/doc/gdbint.texinfo	2001/07/17 20:48:53
> @@ -126,7 +126,7 @@ to debugger commands.
>
>  @value{GDBN} should be relatively permissive, such as for expressions.
>  While the compiler should be picky (or have the option to be made
> -picky), since source code lives for a long time usuazlly, the
> +picky), since source code lives for a long time usually, the
>  programmer doing debugging shouldn't be spending time figuring out to
>  mollify the debugger.
>
> @@ -309,7 +309,7 @@ user says to continue, @value{GDBN} will
>  instruction, single-step, re-insert the trap, and continue on.
>
>  Since it literally overwrites the program being tested, the program area
> -must be writeable, so this technique won't work on programs in ROM.  It
> +must be writable, so this technique won't work on programs in ROM.  It
>  can also distort the behavior of programs that examine themselves,
>  although such a situation would be highly unusual.
>
> @@ -4921,7 +4921,7 @@ owned by the Free Software Foundation" a
>  changes in many programs (not just @value{GDBN}, but GAS, Emacs, GCC,
>  etc) can be
>  contributed with only one piece of legalese pushed through the
> -bureacracy and filed with the FSF.  We can't start merging changes until
> +bureaucracy and filed with the FSF.  We can't start merging changes until
>  this paperwork is received by the FSF (their rules, which we follow
>  since we maintain it for them).
>
>


  reply	other threads:[~2001-07-17 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 13:55 John R. Moore
2001-07-17 13:57 ` John R. Moore [this message]
2001-07-18  0:01 ` 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=Pine.GSO.4.31.0107171356440.25568-100000@cse.cygnus.com \
    --to=jmoore@redhat.com \
    --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