From: Harald Anlauf <anlauf@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: fortran <fortran@gcc.gnu.org>
Subject: Aw: Re: gfortran wiki
Date: Thu, 28 Mar 2024 22:57:24 +0100 [thread overview]
Message-ID: <trinity-18d9d941-bc86-48bf-b082-b78efd9f257a-1711663044143@3c-app-gmx-bap16> (raw)
In-Reply-To: <CAGkQGiKb1C4dVys75DbkB58_5behoe7R9=oXEkBwvpTF+=y5vQ@mail.gmail.com>
Hi Paul,
that's great, thanks!
There is also the other page (https://gcc.gnu.org/fortran/) that is maintained separately via gcc-wwwdocs.
I can try to work on that one, but any help from other is greatly appreciated.
Cheers,
Harald
Gesendet: Donnerstag, 28. März 2024 um 16:45 Uhr
Von: "Paul Richard Thomas" <paul.richard.thomas@gmail.com>
An: "Harald Anlauf" <anlauf@gmx.de>
Cc: "fortran" <fortran@gcc.gnu.org>
Betreff: Re: gfortran wiki
Hi Harald,
I have made a start on this: I have updated the text around bug reports in the developers section, added the bugs fixed etc.. for 2022/23 and eliminated the links to the Doxygen documentation.
The biggest part of the job will be to add "what's new" in 10-14 branches and F2003/8/18 implementation status.
Regards
Paul
On Sun, 24 Mar 2024 at 20:23, Harald Anlauf <anlauf@gmx.de[mailto:anlauf@gmx.de]> wrote:Dear all,
the gfortran wiki (https://gcc.gnu.org/wiki/GFortran[https://gcc.gnu.org/wiki/GFortran]) seems to have been
neglected for quite some time.
Given that the release of gcc 14.1 is to be expected in the near future,
do we want to bring the wiki pages it up-to-date?
Cheers,
Harald
prev parent reply other threads:[~2024-03-28 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 20:23 Harald Anlauf
2024-03-25 17:46 ` Paul Richard Thomas
2024-03-28 15:45 ` Paul Richard Thomas
2024-03-28 21:57 ` Harald Anlauf [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=trinity-18d9d941-bc86-48bf-b082-b78efd9f257a-1711663044143@3c-app-gmx-bap16 \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.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).