From: Janis Johnson <janis187@us.ibm.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Janis Johnson <janis187@us.ibm.com>,
Joe Buck <jbuck@synopsys.com>,
Gcc k6 testing account <caligula@cam029208.student.utwente.nl>,
gcc@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>
Subject: Re: Build status page:Succes and failures.
Date: Thu, 13 Dec 2001 13:15:00 -0000 [thread overview]
Message-ID: <20011213130727.A12581@us.ibm.com> (raw)
In-Reply-To: <Pine.BSF.4.43.0112132123380.99865-100000@pulcherrima.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Thu, Dec 13, 2001 at 09:26:34PM +0100
On Thu, Dec 13, 2001 at 09:26:34PM +0100, Gerald Pfeifer wrote:
>
> > P.S. What's the tool that's supposed to be used now to check the
> > validity of html files?
>
> Personally, I mostly use validator.w3.org. IIRC Zack had a nice
> description on how to perform such a test which was part of a larger
> patch which required some splitting and I believe he didn't have the
> time to commit this part yet...
OK, I found Zack's description in the gcc-patches archives. The file is
clean, although Zack's patch contains an extraneous semicolon in the
html command to use:
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
^ here
Janis
next prev parent reply other threads:[~2001-12-13 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 7:52 Gcc k6 testing account
2001-12-07 9:40 ` Joe Buck
2001-12-12 10:35 ` Janis Johnson
2001-12-13 12:29 ` Gerald Pfeifer
2001-12-13 13:15 ` Janis Johnson [this message]
2001-12-13 16:54 ` Joe Buck
2001-12-13 17:38 ` Janis Johnson
2001-12-15 10:43 ` John Marshall
2001-12-17 9:08 ` Janis Johnson
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
2001-12-12 12:20 ` David Edelsohn
2001-12-12 14:48 ` David Edelsohn
2001-12-12 15:51 ` Joe Buck
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=20011213130727.A12581@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=caligula@cam029208.student.utwente.nl \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=zack@codesourcery.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).