From: Michael Elizabeth Chastain <mec@shout.net>
To: petrs@caldera.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Generalizing compiler invocation for FORTRAN95 testsuite
Date: Fri, 10 May 2002 11:25:00 -0000 [thread overview]
Message-ID: <200205101825.g4AIPaq12948@duracef.shout.net> (raw)
> Should I keep my current compiler support in the F95 testsuite or change
> it temporarily until your work becomes available?
Go ahead and keep your current stuff. If I get my changes into the tree
first, then you can change your compiler selection code. If your changes
go in first, then I will change them when I check in my code.
Michael C
next reply other threads:[~2002-05-10 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:25 Michael Elizabeth Chastain [this message]
2002-05-10 11:38 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 12:19 Michael Elizabeth Chastain
2002-05-08 20:19 Michael Elizabeth Chastain
2002-05-10 11:07 ` Petr Sorfa
2002-05-07 9:20 Michael Elizabeth Chastain
2002-05-07 8:59 Michael Elizabeth Chastain
2002-05-07 9:04 ` Petr Sorfa
2002-05-07 7:55 Petr Sorfa
2002-05-07 9:18 ` Daniel Jacobowitz
2002-05-07 9:27 ` Eli Zaretskii
2002-05-07 9:30 ` Petr Sorfa
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=200205101825.g4AIPaq12948@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@sources.redhat.com \
--cc=petrs@caldera.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