public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alessandro Fanfarillo <fanfarillo.gcc@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>,
		gcc-patches <gcc-patches@gcc.gnu.org>,
	gfortran <fortran@gcc.gnu.org>
Subject: Re: [Fortran, Patch] (RFC, Coarray) Implement TS18508's EVENTS
Date: Thu, 17 Dec 2015 16:19:00 -0000	[thread overview]
Message-ID: <CAHqFgjXBVN0wfJbU3Nfk8WzkjTWEw2--mPYLu-37jwD2Muriuw@mail.gmail.com> (raw)
In-Reply-To: <20151217145703.GA97805@troutmask.apl.washington.edu>

Great! Thanks.

2015-12-17 15:57 GMT+01:00 Steve Kargl <sgk@troutmask.apl.washington.edu>:
> On Thu, Dec 17, 2015 at 01:22:06PM +0100, Alessandro Fanfarillo wrote:
>>
>> I've noticed that this patch has been applied only on trunk and not on
>> the gcc-5-branch. Is it a problem to include EVENTS in gcc-5?
>>
>
> No problem.  When I applied the EVENTS patch to trunk,
> the 5.3 release was being prepared.  I was going to
> wait for a week or two after 5.3 came out, then apply
> the patch.  Now that you have commit access, feel
> free to back port the patch.  Rememer to post the
> patch that you commit to both the fortran and gcc-patches
> list.
>
> --
> Steve

  reply	other threads:[~2015-12-17 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  7:55 Tobias Burnus
2015-11-25 17:25 ` Alessandro Fanfarillo
2015-11-25 19:14   ` Damian Rouson
2015-11-25 22:28   ` Paul Richard Thomas
2015-11-25 22:58     ` Steve Kargl
2015-11-26 16:51   ` Steve Kargl
2015-11-26 17:55     ` Alessandro Fanfarillo
2015-12-02 14:16     ` Alessandro Fanfarillo
2015-12-02 22:00       ` Steve Kargl
2015-12-03 19:46         ` Alessandro Fanfarillo
2015-12-17 12:22         ` Alessandro Fanfarillo
2015-12-17 14:57           ` Steve Kargl
2015-12-17 16:19             ` Alessandro Fanfarillo [this message]
2016-02-11 23:04               ` Alessandro Fanfarillo
2016-02-12 16:32                 ` Alessandro Fanfarillo

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=CAHqFgjXBVN0wfJbU3Nfk8WzkjTWEw2--mPYLu-37jwD2Muriuw@mail.gmail.com \
    --to=fanfarillo.gcc@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    --cc=tobias.burnus@physik.fu-berlin.de \
    /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).