From: FX <fxcoudert@gmail.com>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: Jerry DeLisle <jvdelisle@charter.net>,
Damian Rouson <damian@rouson.net>,
Izaak Beekman <izaak@izaakbeekman.com>,
Andre Vehreschild <vehre@gmx.de>, gfortran <fortran@gcc.gnu.org>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran
Date: Tue, 31 Jan 2017 08:11:00 -0000 [thread overview]
Message-ID: <5924C8A8-45F8-419D-ABB9-EE2B9FBF8364@gmail.com> (raw)
In-Reply-To: <773757770.55906.1485810049667@mail.yahoo.com>
Hi Damian,
> If you're able to join our weekly OpenCoarrays teleconference tomorrow at 10 AM Pacific time, please let me know your gmail address so that I can add you to the call on Hangouts. I really would like to resolve these issues more efficiently than is possible by email. I'm reasonably certain we can either reach a resolution or decide this won't work in the span of a 1-hour teleconference rather than stretching the discussion out over several days by email.
I won’t be able to attend, sorry.
I feel we’ve reached the point where opinion of other maintainers would be good to hear.
FX
next prev parent reply other threads:[~2017-01-31 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 19:37 Jerry DeLisle
2017-01-26 13:25 ` FX
2017-01-26 16:12 ` Jerry DeLisle
2017-01-28 2:13 ` Damian Rouson
2017-01-28 11:22 ` FX
2017-01-28 17:23 ` Jerry DeLisle
2017-01-28 17:56 ` FX
[not found] ` <773757770.55906.1485810049667@mail.yahoo.com>
2017-01-31 8:11 ` FX [this message]
[not found] ` <CAE0_W2VWPN6nxO0eHbRibgT7fu9fwnWAVD_2b_5uxFDpzFAzHg@mail.gmail.com>
2017-01-31 16:36 ` FX
[not found] ` <CAAbnBwaL1m+smdtPsNdoY6u2cyYUbm97qYZBjikL=9GqX3hh-Q@mail.gmail.com>
2017-01-28 18:04 ` FX
2019-02-05 22:08 ` Gfortran GSoC (Was: Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran) Martin Jambor
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=5924C8A8-45F8-419D-ABB9-EE2B9FBF8364@gmail.com \
--to=fxcoudert@gmail.com \
--cc=damian@rouson.net \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=izaak@izaakbeekman.com \
--cc=jvdelisle@charter.net \
--cc=vehre@gmx.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).