public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: loewis@informatik.hu-berlin.de To: gcc-gnats@gcc.gnu.org Subject: web/6441: Pages are not XHTML Date: Wed, 24 Apr 2002 12:16:00 -0000 [thread overview] Message-ID: <20020424191123.5127.qmail@sources.redhat.com> (raw) >Number: 6441 >Category: web >Synopsis: Pages are not XHTML >Confidential: no >Severity: non-critical >Priority: low >Responsible: gerald >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Wed Apr 24 12:16:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: loewis@informatik.hu-berlin.de >Release: unknown-1.0 >Organization: >Environment: >Description: The page http://gcc.gnu.org/gcc-3.1/changes.html claims to be valid XHTML, but as of today, it is not. The validator complains start with * Line 155, column 4: </ul> ^ Error: end tag for element "ul" which is not open; try removing the end tag or check for improper nesting of elements >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-04-24 19:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-24 12:16 loewis [this message] 2002-04-26 6:22 gerald
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=20020424191123.5127.qmail@sources.redhat.com \ --to=loewis@informatik.hu-berlin.de \ --cc=gcc-gnats@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: linkBe 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).