From: Jerry DeLisle <jvdelisle@verizon.net>
To: NightStrike <nightstrike@gmail.com>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch, fortran]PR25829 Add support for F2003 I/O features
Date: Sat, 05 Apr 2008 17:58:00 -0000 [thread overview]
Message-ID: <1207416945.2963.19.camel@lenova.localdomain> (raw)
In-Reply-To: <b609cb3b0804050929u53abf108w8e96a5faeedbb0cd@mail.gmail.com>
On Sat, 2008-04-05 at 12:29 -0400, NightStrike wrote:
> On 4/5/08, Jerry DeLisle <jvdelisle@verizon.net> wrote:
> > After the commit, I will start on the items identified by Tobias.
> >
> > Thanks for review and test case examples.
> >
> > Jerry
> >
> >
>
> Could you also update the Wiki: http://gcc.gnu.org/wiki/Fortran2003 ?
>
> I ask only because I am actively using that wiki to demonstrate the
> current status and capability of gfortran over other solutions.
Yes, we plan to do so.
Jerry
next prev parent reply other threads:[~2008-04-05 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 12:21 Tobias Burnus
2008-04-05 16:30 ` Jerry DeLisle
2008-04-05 17:31 ` NightStrike
2008-04-05 17:58 ` Jerry DeLisle [this message]
[not found] ` <47F7FE02.3070407@net-b.de>
[not found] ` <1207454811.15229.2.camel@lenova.localdomain>
2008-04-06 10:00 ` Tobias Burnus
-- strict thread matches above, loose matches on Subject: below --
2008-04-01 21:10 Tobias Burnus
2008-04-04 4:53 ` Jerry DeLisle
2008-03-29 17:45 Tobias Burnus
2008-03-29 19:57 ` Jerry DeLisle
2008-04-01 4:31 ` Jerry DeLisle
2008-04-01 11:47 ` Tobias Burnus
2008-04-01 14:15 ` Jerry DeLisle
[not found] ` <47F494AC.30003@net-b.de>
2008-04-05 9:24 ` Jerry DeLisle
2008-04-05 9:27 ` Jerry DeLisle
2008-04-01 14:15 ` Jerry DeLisle
2008-03-16 21:48 Jerry DeLisle
2008-03-16 22:03 ` FX Coudert
2008-03-17 0:25 ` Jerry DeLisle
2008-03-17 7:52 ` Janne Blomqvist
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=1207416945.2963.19.camel@lenova.localdomain \
--to=jvdelisle@verizon.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.com \
--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).