From: rth@cygnus.com (Richard Henderson)
To: Per Bothner <bothner@cygnus.com>
Cc: Daniel Karipides <karipid@mae.cornell.edu>, egcs@cygnus.com
Subject: Re: viewing <> constructs via the web archive
Date: Sat, 18 Apr 1998 01:43:00 -0000 [thread overview]
Message-ID: <19980418014326.27822@lisa.cygnus.com> (raw)
In-Reply-To: <199804180206.TAA09308@cygnus.com>
On Fri, Apr 17, 1998 at 07:06:50PM -0700, Per Bothner wrote:
> > This is due to the fact that the <stdio.h> in "#include <stdio.h>"
> > gets interpreted as an unknown HTML tag and is not printed.
>
> The correct fix would seem for the script be to replace all instances of
> '<' by '<'. The characters '&' and '>' should also be replaced the
> same way.
This was explicitly disabled so as not to horribly mung patches
sent to the list.
r~
next prev parent reply other threads:[~1998-04-18 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-17 14:49 Daniel Karipides
1998-04-17 22:05 ` Per Bothner
1998-04-18 1:43 ` Richard Henderson [this message]
1998-04-18 9:08 ` Per Bothner
1998-04-19 18:10 ` Joe Buck
1998-04-25 17:40 ` Gerald Pfeifer
1998-04-25 21:42 ` Jeffrey A Law
1998-04-18 8:18 Daniel Egger
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=19980418014326.27822@lisa.cygnus.com \
--to=rth@cygnus.com \
--cc=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=karipid@mae.cornell.edu \
/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).