From: Elena Zannoni <ezannoni@redhat.com>
To: Bernard Giroud <bgiroud@free.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Submission of patches for Cobol support
Date: Fri, 10 Jan 2003 14:17:00 -0000 [thread overview]
Message-ID: <15902.55033.175840.42670@localhost.redhat.com> (raw)
In-Reply-To: <3E1EB907.4334F604@free.fr>
Bernard Giroud writes:
> I implemented a (partial) support for
> Cobol based on what is produced by
> TinyCobol in a previous version of
> GDB.
>
> What procedure should be followed to
> submit my patches ?
>
> Thanks in advance.
>
> --
> Bernard Giroud , TinyCobol Developer
>
Excellent.
See the submissions of support for other languages,
such as objective-c, and ada:
http://sources.redhat.com/ml/gdb-patches/2002-09/msg00394.html
http://sources.redhat.com/ml/gdb/2002-09/msg00059.html
http://sources.redhat.com/ml/gdb-patches/2002-04/msg01110.html
Most important thing is the FSF copyright assignment.
Elena
prev parent reply other threads:[~2003-01-10 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 12:08 Bernard Giroud
2003-01-10 14:17 ` Elena Zannoni [this message]
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=15902.55033.175840.42670@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=bgiroud@free.fr \
--cc=gdb-patches@sources.redhat.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