From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com, petrs@caldera.com
Subject: Re: [RFH] F95 expression parser
Date: Fri, 10 May 2002 11:33:00 -0000 [thread overview]
Message-ID: <15580.4684.15726.307469@localhost.redhat.com> (raw)
In-Reply-To: <200205101827.g4AIRu913183@duracef.shout.net>
Michael Elizabeth Chastain writes:
> > 1) Should I submit it first to FSF for approval? I assume so.
>
> Yes, but there seems to be some confusion here. Sending work to
> "gdb-patches" is the way you send it to the FSF.
>
> > 2) Should a separate branch be created for the F95 support?
> > Currently I don't think this is necessary.
>
> I don't think so either, because it's not going to break any
> existing code (including F77 code).
>
> Michael C
Maybe look at the gdb-patches archives for how Pierre Muller sumitted
Pascal support? That went pretty smooth.
Elena
next prev parent reply other threads:[~2002-05-10 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:27 Michael Elizabeth Chastain
2002-05-10 11:33 ` Elena Zannoni [this message]
2002-05-10 13:20 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 11:16 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=15580.4684.15726.307469@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--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