From: "Andrea 'Fyre Wyzard' Bocci" <fwyzard@inwind.it>
To: Juan Altmayer Pizzorno <juan@port25.com>,
Terry Flannery <terry.flannery@btinternet.com>,
GCC <gcc@gcc.gnu.org>
Subject: Re: Broken link in http://gcc.gnu.org/releases.html
Date: Sat, 27 Jul 2002 12:59:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20020727083712.00b33a88@popmail.inwind.it> (raw)
In-Reply-To: <20020727082502.B1974@port25.com>
[-- Attachment #1: Type: text/plain, Size: 35 bytes --]
Here's a patch to fix it.
fwyzard
[-- Attachment #2: Type: text/plain, Size: 1081 bytes --]
Index: releases.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/releases.html,v
retrieving revision 1.34
diff -c -2 -p -r1.34 releases.html
*** releases.html 26 Jul 2002 22:01:10 -0000 1.34
--- releases.html 27 Jul 2002 06:37:02 -0000
*************** opposed to development snapshots).</p>
*** 35,39 ****
<tr><th>Release Name</th><th>Version number</th><th>Release date</th></tr>
! <tr><td><a href="gcc-3.1.1/">GCC 3.1</a></td><td>3.1.1</td> <td>July 26, 2002</td></tr>
<tr><td><a href="gcc-3.1/">GCC 3.1</a></td><td>3.1</td> <td>May 15, 2002</td></tr>
<tr><td><a href="gcc-3.0/">GCC 3.0.4</a></td><td>3.0.4</td> <td>February 20, 2002</td></tr>
--- 35,39 ----
<tr><th>Release Name</th><th>Version number</th><th>Release date</th></tr>
! <tr><td><a href="gcc-3.1/">GCC 3.1.1</a></td><td>3.1.1</td> <td>July 26, 2002</td></tr>
<tr><td><a href="gcc-3.1/">GCC 3.1</a></td><td>3.1</td> <td>May 15, 2002</td></tr>
<tr><td><a href="gcc-3.0/">GCC 3.0.4</a></td><td>3.0.4</td> <td>February 20, 2002</td></tr>
next prev parent reply other threads:[~2002-07-27 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 12:35 Juan Altmayer Pizzorno
2002-07-27 12:59 ` Andrea 'Fyre Wyzard' Bocci [this message]
2002-07-29 8:48 ` 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=5.1.0.14.2.20020727083712.00b33a88@popmail.inwind.it \
--to=fwyzard@inwind.it \
--cc=gcc@gcc.gnu.org \
--cc=juan@port25.com \
--cc=terry.flannery@btinternet.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).