From: Aidan Skinner <aidan@velvet.net>
To: gdb-patches@sources.redhat.com
Subject: [RFC] Ada Support Plan
Date: Sat, 27 Apr 2002 18:39:00 -0000 [thread overview]
Message-ID: <20020428023948.D3067@velvet.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Evening all. I got the copyright assignment forms back from the FSF
today. :)
So I've been thinking about how to go about feeding the patches to the
list, and basically came up with this:
1. patches to files that the ada-* files need (I *think* this is a
no-op, but I'm checking atm).
2. patches for the ada-* files and Makefile.in
3. patches for enabling ada support in the internals
4. patches to "set lang ada" and detect when to go into ada mode.
Does this seem reasonable? Is there a better way of doing it?
- Aidan
--
aidan@velvet.net http://www.velvet.net/~aidan/ aim:aidans42
finger for pgp key fingerprint |Unix Programmer/Admin actively seeking work
01AA 1594 2DB0 09E3 B850 |CV at http://www.velvet.net/~aidan/cv.txt
C2D0 9A2C 4CC9 3EC4 75E1 |Gis a job, go on, I can do that, go on, gis it.
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next reply other threads:[~2002-04-28 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 18:39 Aidan Skinner [this message]
2002-04-28 14:52 ` Paul Hilfinger
2002-04-28 15:38 ` Aidan Skinner
2002-05-01 7:13 ` Andrew Cagney
2002-05-01 16:08 ` Aidan Skinner
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=20020428023948.D3067@velvet.net \
--to=aidan@velvet.net \
--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