This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: merge gcc-2.95/{gcc-2.95.html,gcc-2.95.1.html,gcc-2.95.2.html,gcc-2.95.3.html}
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: gcc-patches at gcc dot gnu dot org
- Cc: "Andrea 'Fyre Wyzard' Bocci" <fwyzard at inwind dot it>
- Date: Sat, 26 Jan 2002 00:23:48 +0100 (CET)
- Subject: Re: PATCH: merge gcc-2.95/{gcc-2.95.html,gcc-2.95.1.html,gcc-2.95.2.html,gcc-2.95.3.html}
On Sat, 26 Jan 2002, Gerald Pfeifer wrote:
> And here is the analogous patch for GCC 2.95:
>
> Merge gcc-2.95/{gcc-2.95.html,gcc-2.95.1.html,gcc-2.95.2.html,
> gcc-2.95.3.html} to gcc-2.95/index.html and gcc-2.95/features.html
> Provide proper redirects and update the releases page accordingly.
Andrea, I fixed several XHTML issues with this patch, but there's still
quite a bit missing (especially </li>s).
And here is the patch that updates releasing.html accordingly:
We do not need to deal with separate announcement pages for minor
releases any longer.
Gerald
Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.5
diff -u -3 -p -r1.5 releasing.html
--- releasing.html 2002/01/19 12:48:34 1.5
+++ releasing.html 2002/01/25 23:22:01
@@ -9,11 +9,8 @@
<ol>
<li>Before rolling the release, update the release notes web pages and
-ensure that they are all listed in <code>contrib/gennews</code>. If
-using separate announcement pages for each minor release, as with GCC
-2.95, a new release announcement page such as
-<code>gcc-2.95/gcc-2.95.4.html</code> should be created to describe
-the changes in the release. If using an overall announcement page for
+ensure that they are all listed in <code>contrib/gennews</code>.
+If using an overall announcement page for
successive minor releases, as with GCC 3.0, this should note the new
release without removing information about any previous minor releases
in that series, and the <code>features.html</code> page for that