From: Arjen Markus <arjen.markus895@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Fortran List <fortran@gcc.gnu.org>
Subject: Re: F2018 C937
Date: Thu, 19 Aug 2021 17:10:47 +0200 [thread overview]
Message-ID: <CAMCbSMqtUGT405YcRnrgNQtjSh1PS=t6TVF=UHqGs4vKarLR+w@mail.gmail.com> (raw)
In-Reply-To: <CAMCbSMqJzrD8wor760fgm7iKLqG7+_ZsCxRvfnF2sT1Tj+gdaQ@mail.gmail.com>
I have applied the patches locally (take care to restore the tabs ;)).
Should I now commit these changes or is there a more formal procedure
involved?
Regards,
Arjen
Op do 19 aug. 2021 om 08:59 schreef Arjen Markus <arjen.markus895@gmail.com
>:
> Hi Steve,
>
> I am willing to take up this challenge ;), as well as the patch for C949.
> It would be my next attempt to get acquainted with the source code (a first
> step hopefully to actively contribute).
>
> Regards,
>
> Arjen
>
> Op di 17 aug. 2021 om 21:02 schreef Steve Kargl via Fortran <
> fortran@gcc.gnu.org>:
>
>> For those that might care, I draw your attention to
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101951
>>
>> Good opportunity for a lurker to step forward and
>> become a gfortran committer. Otherwise, this patch
>> will fester in bugzilla the dozen or so other patches
>> I've attached to PRs.
>>
>> --
>> Steve
>>
>
next prev parent reply other threads:[~2021-08-19 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 19:01 Steve Kargl
2021-08-19 6:59 ` Arjen Markus
2021-08-19 15:10 ` Arjen Markus [this message]
2021-08-19 16:23 ` Steve Kargl
2021-08-20 6:36 ` Arjen Markus
2021-08-20 6:46 ` Steve Kargl
2021-08-20 6:49 ` Arjen Markus
2021-08-23 17:18 ` Steve Kargl
2021-08-23 18:37 ` Arjen Markus
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='CAMCbSMqtUGT405YcRnrgNQtjSh1PS=t6TVF=UHqGs4vKarLR+w@mail.gmail.com' \
--to=arjen.markus895@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).