public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Bernard Dautrevaux <Dautrevaux@microprocess.com>
Cc: Ken Whaley <ken@believe.com>, Sergey Ostrovsky <sostrovs@kns.com>,
	"H . J . Lu" <hjl@lucon.org>,
	gcc@gcc.gnu.org
Subject: Re: Compiler for Red Hat Linux 8
Date: Thu, 19 Jul 2001 01:16:00 -0000	[thread overview]
Message-ID: <3B56979A.6A45A932@moene.indiv.nluug.nl> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E2EB@IIS000>

Bernard Dautrevaux wrote:

[ This is getting off-topic fast, but one time more ... ]

> I'm not sure I understand you: I get the original mail from Ken (through the
> mailing list of course) with proper quotes! It seems it's YOUR Operating
> System Of Choice (or one of the mail relays between the mailing list and
> your system) that replace quotes with question marks...

This is how my inbox sees the quotes of the text Ken sent:

<QUOTE>
I\x92ve just gone through this process, pretty much exactly
as Sergey described, including digging around trying to
find info on what patches, versions, etc. of the tools
are required, and agree that it\x92s a sort of black magic.
Saying \x93use an official released version to build your
system\x94 becomes a lot more palatable if there would always
</QUOTE>

Doesn't look like the ASCII ' encoding to me ...

[ If you're still not convinced, I can send you an `od' dump of the mail
]

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

  reply	other threads:[~2001-07-19  1:16 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19  0:29 Bernard Dautrevaux
2001-07-19  1:16 ` Toon Moene [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19 23:16 Bernard Dautrevaux
2001-07-19 10:49 dewar
2001-07-19  4:33 dewar
2001-07-19  1:36 Bernard Dautrevaux
2001-07-19  2:40 ` Joseph S. Myers
2001-07-19  3:02 ` Roman Zippel
2001-07-19  3:12 ` Russ Allbery
2001-07-18 20:02 dewar
2001-07-18 14:41 dewar
2001-07-18 15:29 ` Geoff Keating
2001-07-18 17:50   ` Joe Buck
2001-07-18 18:59 ` Michael Eager
2001-07-18 19:26   ` Justin Guyett
2001-07-19  9:05     ` Mark Mitchell
2001-07-19 19:28   ` akbar A.
2001-07-18 22:10 ` Per Bothner
2001-07-18 22:19   ` Joe Buck
2001-07-18 22:38     ` Per Bothner
2001-07-18 23:00       ` Alex Rosenberg
2001-07-19 14:05       ` Jonathan Larmour
2001-07-18 14:33 Geoff Keating
2001-07-18 13:21 Benjamin Kosnik
2001-07-17 20:00 Benjamin Kosnik
2001-07-17 17:37 mike stump
2001-07-17 13:04 Geoff Keating
2001-07-17 15:52 ` Joe Buck
2001-07-17 17:48   ` Per Bothner
2001-07-18  8:55     ` Joseph S. Myers
2001-07-17 18:24 ` Craig Rodrigues
2001-07-18  2:41 ` Andreas Jaeger
2001-07-18  9:03   ` H . J . Lu
2001-07-18 12:01     ` Joe Buck
2001-07-18 12:46       ` H . J . Lu
2001-07-18 13:22         ` Joe Buck
2001-07-18 13:31           ` H . J . Lu
2001-07-18 14:28             ` David Edelsohn
2001-07-18 15:03               ` Joern Rennecke
2001-07-18 15:12                 ` David Edelsohn
2001-07-18 15:24                   ` Joe Buck
2001-07-18 17:05                     ` H . J . Lu
2001-07-19  4:56                     ` Toon Moene
2001-07-18 15:41                 ` Joseph S. Myers
2001-07-18 16:23                   ` H . J . Lu
2001-07-18 12:18     ` Sergey Ostrovsky
2001-07-18 15:19       ` Ken Whaley
2001-07-18 15:30         ` Toon Moene
2001-07-18 15:59           ` Ken Whaley
2001-07-18 16:08             ` Toon Moene
2001-07-18 13:30   ` Gerald Pfeifer
2001-07-19  5:17     ` Andreas Jaeger
2001-07-19 12:23       ` Gerald Pfeifer
2001-07-18 19:07   ` LinuxVN
2001-07-18 13:44 ` Toon Moene

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=3B56979A.6A45A932@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=Dautrevaux@microprocess.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.org \
    --cc=ken@believe.com \
    --cc=sostrovs@kns.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).