From: Gerald Pfeifer <gerald@pfeifer.com>
To: Rob Myers <chief-webmaster@gnu.org>
Cc: gcc@gnu.org, fortran@gcc.gnu.org
Subject: Re: Updating gnu.org/software Fortran Page
Date: Sun, 13 Sep 2009 19:59:00 -0000 [thread overview]
Message-ID: <alpine.LSU.1.99.0909132153110.15831@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <49F0C3E2.8060609@gnu.org>
Rob,
On Thu, 23 Apr 2009, Rob Myers wrote:
> The gnu.org webmaster team are going to be updating all the pages in the
> gnu.org/software subdirectory, which includes -
>
> http://www.gnu.org/software/fortran
>
> This will involve changing the design of the page to match the new style
> of gnu.org, and updating the information about the GNU Fortran project
> if possible.
>
> Is there any information you would like adding to the project page or
> any other changes you would like making to its content?
I noticed this page now has a broken link to
http://www.gnu.org/software/gcc/gcc.html
which I believe is due to you guys now redirecting to gcc.gnu.org instead
of mirroring the actual pages.
You may want to adjust the link to http://www.gnu.org/software/gcc/
instead, for example.
Also, let me include our dedicate list fortran@gcc.gnu.org and provide
the text this crew is using for their own description:
Gfortran is the name of the GNU Fortran project, developing a free
Fortran 95/2003 compiler for GCC, the GNU Compiler Collection. The
gfortran development effort uses an open development environment in
order to attract a larger team of developers and to ensure that gfortran
can work on multiple architectures and diverse environments.
You may want to reuse that.
One thing I noticed is that your page really referes to g77 when we now
provide a more modern Fortran frontend. So, I would not refer to g77 at
all, and also adjust the link your current have to "the online g77
documentation" to instead refer to
http://gcc.gnu.org/onlinedocs/ref/gfortran/
which will also redirect to the documentation of the latest released
version. (Do not follow the redirect, but really use the link as I
specified it.)
Hope this helps,
Gerald
prev parent reply other threads:[~2009-09-13 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 22:48 Rob Myers
2009-09-13 19:59 ` Gerald Pfeifer [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=alpine.LSU.1.99.0909132153110.15831@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=chief-webmaster@gnu.org \
--cc=fortran@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).