From: Tom Tromey <tromey@redhat.com>
To: Craig Rodrigues <rodrigc@mediaone.net>
Cc: Tommy Dugandzic <tommy@mensa.se>, gcc@gnu.org
Subject: Re: Typo.
Date: Sat, 02 Feb 2002 18:55:00 -0000 [thread overview]
Message-ID: <87g04jl0ga.fsf@creche.redhat.com> (raw)
In-Reply-To: Craig Rodrigues's message of "Sat, 2 Feb 2002 21:49:55 -0500"
>>>>> "Craig" == Craig Rodrigues <rodrigc@mediaone.net> writes:
Tommy> s/optimised/optimized/
Tom> Thanks, I'll check in a fix for this shortly.
Craig> Why? "Optimized" is the spelling that is currently used throughout
Craig> the GCC documentation.
My patch changed the text from "ise" to "ize".
Tom
next prev parent reply other threads:[~2002-02-03 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 15:26 Typo Tommy Dugandzic
2002-02-02 13:24 ` Typo Erik Mouw
2002-02-02 15:57 ` Typo Alexandre Oliva
2002-02-02 18:22 ` Typo Tom Tromey
2002-02-02 18:48 ` Typo Craig Rodrigues
2002-02-02 18:55 ` Tom Tromey [this message]
2002-01-31 15:30 Typo Tommy Dugandzic
2002-02-02 18:23 ` Typo Tom Tromey
2002-02-02 14:42 Typo Robert Dewar
2002-02-02 15:23 ` Typo Erik Mouw
2002-02-02 18:45 ` Typo John Levon
2002-02-02 15:24 Typo Robert Dewar
2002-02-02 15:35 ` Typo Kevin Handy
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=87g04jl0ga.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc@gnu.org \
--cc=rodrigc@mediaone.net \
--cc=tommy@mensa.se \
/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).