From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Daniel Burrows <dnb114@psu.edu>
Cc: gcc@gnu.org, <gcc-patches@gcc.gnu.org>
Subject: PATCH for Re: Broken link on gcc.gnu.org frontpage
Date: Tue, 23 Jul 2002 10:57:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0207231442470.18054-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20020721202523.GA3792@torrent>
On Sun, 21 Jul 2002, Daniel Burrows wrote:
> The frontpage says:
>
> "Pending release series: GCC 3.2 scheduled for 2002-07-2x"
>
> GCC 3.2 is a link to http://gcc.gnu.org/gcc-3.2/ -- but when I visit
> that link, I get a 403 Forbidden error. gcc@gnu.org is the contact address
> listed on the page, so I'm sending this message to you :)
Fix thusly, with a few additional tweaks.
(This main GCC 3.2 page will contain a relatively generic announcement
and will be added only directly before the actual release, but the patch
below adds a proper link for now.)
Gerald
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.323
diff -u -3 -p -r1.323 index.html
--- index.html 22 Jul 2002 10:00:46 -0000 1.323
+++ index.html 23 Jul 2002 12:50:26 -0000
@@ -157,7 +157,7 @@ and automated testers</a> to maintain an
</dd>
<dt><strong>Pending release series:</strong>
- <a href="gcc-3.2/">GCC 3.2</a> scheduled for 2002-07-2x
+ <a href="gcc-3.2/changes.html">GCC 3.2</a> scheduled for 2002-07-2x
</dt><dd>
<br />
Changes require approval by release manager.
@@ -173,7 +173,7 @@ and automated testers</a> to maintain an
-->
<dt><strong>Active development (mainline):</strong>
- will become GCC 3.3
+ will become <a href="gcc-3.3/changes.html">GCC 3.3</a>
</dt><dd>
<a href="develop.html#stage2">Stage 2</a>; open for all maintainers.
</dd>
Index: gcc-3.2/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/changes.html,v
retrieving revision 1.23
diff -u -3 -p -r1.23 changes.html
--- gcc-3.2/changes.html 21 Jul 2002 10:55:13 -0000 1.23
+++ gcc-3.2/changes.html 23 Jul 2002 12:50:26 -0000
@@ -14,11 +14,11 @@
<h2>Caveats</h2>
<ul>
- <li>This GCC release is based on the GCC 3.1 sourcebase,
- but it has a number of C++ ABI fixes in it. As a result,
- the C++ comiler in this release is binary incompatible with
- the C++ compilers found in earlier GCC releases, including
- GCC 3.1 and GCC 3.1.1.</li>
+ <li>This GCC release is based on the GCC 3.1 sourcebase, and thus has
+ all the <a href="../gcc-3.1/changes.html">changes in the GCC 3.1 series</a>.
+ In addition, GCC 3.1 has a number of C++ ABI fixes in it which make its C++
+ compiler binary incompatible with the C++ compilers found in earlier GCC
+ releases, including GCC 3.1 and GCC 3.1.1.</li>
</ul>
next prev parent reply other threads:[~2002-07-23 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 16:20 Daniel Burrows
2002-07-23 10:57 ` Gerald Pfeifer [this message]
2002-07-23 21:44 ` PATCH for " Mike Stump
2002-07-24 9:01 ` Gerald Pfeifer
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=Pine.BSF.4.44.0207231442470.18054-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=dnb114@psu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=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: 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).