From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7376 invoked by alias); 28 Apr 2002 01:39:50 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7357 invoked from network); 28 Apr 2002 01:39:48 -0000 Received: from unknown (HELO crushed.velvet.net) (62.49.231.23) by sources.redhat.com with SMTP; 28 Apr 2002 01:39:48 -0000 Received: from aidan by crushed.velvet.net with local (Exim 3.33 #1) id 171dfI-0001QW-00 for gdb-patches@sources.redhat.com; Sun, 28 Apr 2002 02:39:48 +0100 Date: Sat, 27 Apr 2002 18:39:00 -0000 From: Aidan Skinner To: gdb-patches@sources.redhat.com Subject: [RFC] Ada Support Plan Message-ID: <20020428023948.D3067@velvet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4jXrM3lyYWu4nBt5" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-SW-Source: 2002-04/txt/msg01110.txt.bz2 --4jXrM3lyYWu4nBt5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 829 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 --=20 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. --4jXrM3lyYWu4nBt5 Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 230 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (OpenBSD) Comment: For info see http://www.gnupg.org iD8DBQE8y1LjmixMyT7EdeERArS9AJ46DzKDPjQThC5aacJRrWblDIRXmACeOqZg slVLmJ38JfNtOUl210ABAQM= =0Sup -----END PGP SIGNATURE----- --4jXrM3lyYWu4nBt5--