public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Urs Janßen <urs@akk.org>
To: gcc@gcc.gnu.org
Subject: Typo on http://gcc.gnu.org/cvs.html
Date: Fri, 16 Aug 2002 16:37:00 -0000	[thread overview]
Message-ID: <20020816233723.GA24252@akk10.akk.uni-karlsruhe.de> (raw)

--- cvs.html.o	Sat Aug 17 01:34:44 2002
+++ cvs.html.n	Sat Aug 17 01:35:38 2002
@@ -115,7 +115,7 @@
 
 <p>There has been some discussion of removing these generated files
 from GCC's CVS source tree (there is no discussion of removing them
-from them from the released source tarballs).  If that happens then
+from the released source tarballs).  If that happens then
 building GCC from the CVS source tree would require installing 
 the above mentioned build tools.  Installing these build tools is not
 particularly difficult, but can be time consuming especially if you 

             reply	other threads:[~2002-08-16 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 16:37 Urs Janßen [this message]
2002-08-19  9:47 ` Janis Johnson
2004-10-11  8:22 ian
2004-10-11  9:45 ` Paolo Bonzini

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=20020816233723.GA24252@akk10.akk.uni-karlsruhe.de \
    --to=urs@akk.org \
    --cc=gcc@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).