public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: janis187@us.ibm.com (Janis Johnson)
Cc: pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer),
	Joe.Buck@synopsys.COM (Joe Buck),
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PATCH for Re: web page starting to show its age
Date: Wed, 30 Oct 2002 16:20:00 -0000	[thread overview]
Message-ID: <200210302157.g9ULvk525568@piper.synopsys.com> (raw)
In-Reply-To: <20021030133725.A2044@us.ibm.com> from "Janis Johnson" at Oct 30, 2002 01:37:25 PM

I wrote:
> > > There are several things about the web page gcc.gnu.org that are beginning
> > > to show their age and should be revised.  Take the first paragraph:
> > > [...]

Janis writes:
> How's this?  (Yes, I'm now a web page maintainer, but I'm not going to
> make this change without running it by people first).

Fine with me.

> +<p>GCC is the GNU Compiler Collection, which currently contains
> +front ends for C, C++, Objective C, Fortran,
>  <a href="java/">Java</a>, and Ada, as well as libraries for these
>  languages (<a href="libstdc++/">libstdc++</a>, libgcj,...).</p>
> +
> +<p>Major decisions about GCC are made by the <a href="steering.html">
> +steering committee</a>, guided by the <a href="gccmission.html">
> +mission statement</a>.  That group began as the egcs steering
> +committee and in April 1999 was appointed by the FSF as the official
> +GNU maintainer for GCC.

  reply	other threads:[~2002-10-30 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 22:28 Joe Buck
2002-10-04  7:16 ` PATCH for " Gerald Pfeifer
2002-10-30 14:58   ` Janis Johnson
2002-10-30 16:20     ` Joe Buck [this message]
2002-10-30 16:44       ` Gerald Pfeifer
2002-10-30 20:41         ` Janis Johnson
2002-10-04  7:21 ` Gerald Pfeifer
2002-10-05 13:03 ` Toon Moene

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=200210302157.g9ULvk525568@piper.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=Joe.Buck@synopsys.COM \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).