From: Harald Anlauf <anlauf@gmx.de>
To: Jerry D <jvdelisle2@gmail.com>,
Alexander Westbrooks <ctechnodev@gmail.com>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PR82943 - Suggested patch to fix
Date: Sat, 20 Jan 2024 21:08:36 +0100 [thread overview]
Message-ID: <bb6473d0-43d0-489d-a842-f592171f5bcd@gmx.de> (raw)
In-Reply-To: <300b5533-685e-45a0-af07-c37884ba604f@gmail.com>
Am 20.01.24 um 20:08 schrieb Jerry D:
> On 1/20/24 10:46 AM, Alexander Westbrooks wrote:
>> Hello and Happy New Year!
>>
>> I wanted to follow up on this patch I made to address PR82943 for
>> GFortran. Has anyone had a chance to review it?
>>
>> Thanks,
>>
>> Alexander Westbrooks
>>
>
> Inserting myself in here just a little bit. I will apply and test today
> if I can. Paul is unavailable for a few weeks. Harald can chime in.
>
> Do you have commit rights for gcc?
I am not aware of Alex having a copyright assignment on file,
or a DCO certificate, and the patch is not signed off.
But I might be wrong.
> Your efforts are appreciated.
>
> Regards,
>
> Jerry
>
>
>
>
next prev parent reply other threads:[~2024-01-20 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 17:17 Alexander Westbrooks
2023-06-28 21:14 ` Harald Anlauf
2023-06-30 3:38 ` Alexander Westbrooks
2023-06-30 4:42 ` Steve Kargl
2023-06-30 6:40 ` Paul Richard Thomas
2023-06-30 9:08 ` Paul Richard Thomas
2023-07-17 15:56 ` Alexander Westbrooks
2024-01-20 18:46 ` Alexander Westbrooks
2024-01-20 19:08 ` Jerry D
2024-01-20 19:52 ` Jerry D
2024-01-20 20:08 ` Harald Anlauf [this message]
2024-01-20 20:37 ` Jerry D
2024-01-20 21:40 ` Harald Anlauf
2024-01-20 22:42 ` Alexander Westbrooks
2024-01-21 20:55 ` Harald Anlauf
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=bb6473d0-43d0-489d-a842-f592171f5bcd@gmx.de \
--to=anlauf@gmx.de \
--cc=ctechnodev@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle2@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).