From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, petrs@caldera.com
Subject: Re: [RFH] F95 Testsuite
Date: Fri, 10 May 2002 11:24:00 -0000 [thread overview]
Message-ID: <200205101824.g4AIOa212809@duracef.shout.net> (raw)
> 1) Do I need to send it to FSF?
No, we can handle it through these channels.
Someone such as AndrewC or JimB needs to check that you have an FSF
assignment on file for this work.
> 2) Can I create the gdb.f95 directory or does some else need to do it?
Errr, I don't know, another AndrewC question.
> 3) Do I need to send the whole F95 testsuite for review at
> gdb-patches@sources.redhat.com?
For something this big, a URL pointing a tarball would be useful.
Michael C
next reply other threads:[~2002-05-10 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:24 Michael Elizabeth Chastain [this message]
2002-05-10 13:15 ` Jim Blandy
2002-05-10 13:21 ` Petr Sorfa
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 11:02 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=200205101824.g4AIOa212809@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