From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Daniel Santos <daniel.santos@pobox.com>, gcc <gcc@gcc.gnu.org>,
Uros Bizjak <ubizjak@gmail.com>
Subject: Re: GCC 8.1 Released
Date: Wed, 02 May 2018 17:35:00 -0000 [thread overview]
Message-ID: <CAH6eHdTwACgmP-+Fe=U_ej4eO4QxaUR_4NtQ=C6MJjLzn0eu+w@mail.gmail.com> (raw)
In-Reply-To: <etPan.5ae9f37f.1edf93a5.6012@sourceryinstitute.org>
On 2 May 2018 at 18:21, Damian Rouson wrote:
> Could someone please point me to instructions for how to submit a change to the gfortran changes list?
The web pages are hosted in CVS and patches for them are handled like
any other GCC patches:
https://gcc.gnu.org/about.html#cvs
next prev parent reply other threads:[~2018-05-02 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180502121545.GU8577@tucnak>
2018-05-02 16:37 ` Daniel Santos
2018-05-02 16:43 ` Jakub Jelinek
2018-05-02 17:21 ` Damian Rouson
2018-05-02 17:35 ` Jonathan Wakely [this message]
2018-05-02 18:02 ` Jim Wilson
2018-05-02 12:16 Jakub Jelinek
2018-05-04 6:23 ` Bert Wesarg
2018-05-04 6:31 ` Janne Blomqvist
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='CAH6eHdTwACgmP-+Fe=U_ej4eO4QxaUR_4NtQ=C6MJjLzn0eu+w@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=damian@sourceryinstitute.org \
--cc=daniel.santos@pobox.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ubizjak@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).