From: Janis Johnson <janis187@us.ibm.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Subject: Re: update active versions on GCC home page
Date: Tue, 17 Dec 2002 10:36:00 -0000 [thread overview]
Message-ID: <20021217091706.A1460@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212170314490.13448-100000@kern.srcf.societies.cam.ac.uk>; from jsm28@cam.ac.uk on Tue, Dec 17, 2002 at 03:16:01AM +0000
On Tue, Dec 17, 2002 at 03:16:01AM +0000, Joseph S. Myers wrote:
> On Mon, 16 Dec 2002, Janis Johnson wrote:
>
> > The list of releases on the GCC home page is out of date, and Gerald is
> > gone for another week. Mark, does this change look OK?
>
> Please also add updating the home page to the list in branching.html.
Done, with the following patch:
Index: branching.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v
retrieving revision 1.7
diff -u -r1.7 branching.html
--- branching.html 24 Sep 2002 03:44:43 -0000 1.7
+++ branching.html 17 Dec 2002 17:11:22 -0000
@@ -36,6 +36,10 @@
<code>criteria.html</code>. Update the toplevel
<code>buildstat.html</code> to refer to this version.</li>
+<li>Update the <code>index.html</code> web page to show the new active
+release branch, the current release series, and active development
+(mainline). Update the version and development stage for mainline.</li>
+
<li>Update <code>f/root.texi</code> on the branch to use <code>@clear
DEVELOPMENT</code>.</li>
prev parent reply other threads:[~2002-12-17 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 17:13 Janis Johnson
2002-12-16 17:28 ` Mark Mitchell
2002-12-16 21:40 ` Joseph S. Myers
2002-12-17 10:36 ` Janis Johnson [this message]
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=20021217091706.A1460@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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).