public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andre Vehreschild <vehre@gmx.de>
To: GCC-Patches-ML <gcc-patches@gcc.gnu.org>
Cc: GCC-Fortran-ML <fortran@gcc.gnu.org>,
	Damian Rouson <damian@sourceryinstitute.org>
Subject: Re: [Backport gcc-11, Patch, Fortran] PR100337 Should be able to pass non-present optional arguments to CO_BROADCAST
Date: Mon, 14 Feb 2022 16:50:54 +0100	[thread overview]
Message-ID: <20220214165054.69fbfc5c@vepi2> (raw)
In-Reply-To: <b64edeb7-927f-6708-2707-b8254c1ec3fd@codesourcery.com>

Hi everyone,

sorry for missing out on the gcc-11 backport, but better late than never. 

Committed backport as ae57aae60d1.

Regards,
	Andre

On Wed, 23 Jun 2021 11:21:45 +0200
Tobias Burnus <tobias@codesourcery.com> wrote:

> On 23.06.21 10:23, Andre Vehreschild wrote:
> 
> > Will wait two weeks for any errors introduced by this patch before
> > backporting to gcc-11, ok?  
> 
> Fine with me.
> 
> Thanks again for the patch.
> 
> Tobias
> 
> -----------------
> Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
> Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
> Thürauf


-- 
Andre Vehreschild * Email: vehre ad gmx dot de 

      reply	other threads:[~2022-02-14 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 13:33 [Patch, " Andre Vehreschild
2021-06-04 16:05 ` [Ping, Patch, " Andre Vehreschild
2021-06-19 11:23   ` [Ping^2, " Andre Vehreschild
2021-06-21 12:30     ` Tobias Burnus
2021-06-22  7:40       ` Andre Vehreschild
2021-06-22  8:37         ` Tobias Burnus
2021-06-23  8:23           ` Andre Vehreschild
2021-06-23  9:21             ` Tobias Burnus
2022-02-14 15:50               ` Andre Vehreschild [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=20220214165054.69fbfc5c@vepi2 \
    --to=vehre@gmx.de \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).