public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gunther Nikl <gni@gecko.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix documentation typos
Date: Thu, 27 Nov 2003 11:41:00 -0000	[thread overview]
Message-ID: <20031127105404.GA62646@lorien.int.gecko.de> (raw)

[This is the second try because the first mail didn't make it]

Hello!

This patch is supposed to correct two typos in the documentation
but I am not sure whether these are really typos. I believe that
'@' characters removed by this patchs are stray ones.

Gunther

--- cut ---

2003-11-27  Gunther Nikl  <gni@gecko.de>

	* doc/cppinternals.texi (Lexing a token):  Fix typo.
	* doc/tm.texi (SYSROOT_HEADERS_SUFFIX_SPEC): Ditto.

diff -rup gcc-3.4/gcc/doc/cppinternals.texi gcc-3.4-gg/gcc/doc/cppinternals.texi
--- gcc-3.4/gcc/doc/cppinternals.texi	Mon Jan  7 20:03:36 2002
+++ gcc-3.4-gg/gcc/doc/cppinternals.texi	Tue Nov 25 14:38:57 2003
@@ -159,7 +159,7 @@ will be removed, so I'll not discuss it 
 The job of @code{_cpp_lex_direct} is simply to lex a token.  It is not
 responsible for issues like directive handling, returning lookahead
 tokens directly, multiple-include optimization, or conditional block
-skipping.  It necessarily has a minor r@^ole to play in memory
+skipping.  It necessarily has a minor role to play in memory
 management of lexed lines.  I discuss these issues in a separate section
 (@pxref{Lexing a line}).
 
diff -rup gcc-3.4/gcc/doc/tm.texi gcc-3.4-gg/gcc/doc/tm.texi
--- gcc-3.4/gcc/doc/tm.texi	Mon Nov 17 09:52:33 2003
+++ gcc-3.4-gg/gcc/doc/tm.texi	Tue Nov 25 14:38:28 2003
@@ -329,7 +329,7 @@ et al, within sysroot+suffix.
 @defmac SYSROOT_HEADERS_SUFFIX_SPEC
 Define this macro to add a headers_suffix to the target sysroot when
 GCC is configured with a sysroot.  This will cause GCC to pass the
-updated sysroot+headers_suffix to CPP@, causing it to search for
+updated sysroot+headers_suffix to CPP, causing it to search for
 usr/include, et al, within sysroot+headers_suffix.
 @end defmac
 
--- cut ---

             reply	other threads:[~2003-11-27 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 11:41 Gunther Nikl [this message]
2003-11-27 12:49 ` Joseph S. Myers
2003-11-27 14:16   ` Gunther Nikl
2003-11-27 14:41     ` Joseph S. Myers
  -- strict thread matches above, loose matches on Subject: below --
2001-12-31 23:28 Typo in c-tree.texi Gaute B Strokkenes
2002-01-05 23:51 ` Unreviewed patch: " Gaute B Strokkenes
2002-01-08  1:43   ` [PATCH] rtl.texi typo fix Gaute B Strokkenes
2002-01-29  4:40     ` Unreviewed patch Gaute B Strokkenes
2002-02-18 22:02       ` [PATCH] Fix documentation typos Gaute B Strokkenes
2002-02-19 10:04         ` Gerald Pfeifer
2002-02-19 12:33           ` Zack Weinberg
2002-02-19 13:07           ` Gaute B Strokkenes
2002-02-19 15:29             ` Gerald Pfeifer

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=20031127105404.GA62646@lorien.int.gecko.de \
    --to=gni@gecko.de \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).