X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Tue, 7 Dec 2004 12:13:58 -0500
Message-Id: <200412071713.iB7HDwwY003103@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <200412071912.29471.pavenis@latnet.lv> (message from Andris
	Pavenis on Tue, 7 Dec 2004 19:12:29 +0200)
Subject: Re: Patches to build GDB 6.3
References: <01c4c987$Blat.v2.2.2$52b9e920 AT zahav DOT net DOT il> <200412071852 DOT 42299 DOT pavenis AT latnet DOT lv> <200412071654 DOT iB7GsYYg002730 AT envy DOT delorie DOT com> <200412071912 DOT 29471 DOT pavenis AT latnet DOT lv>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> About submitting changes for GCC: I still should myself review accumulated 
> changes carefully when I'll have time. Now we see what poked out when I went 
> through updates to djgpp.h. Also I recently I sent some small patches to
> gcc-patches mailing list, but they seem to be lost in flood of other patches.
> 
> Perhaps it should not be too difficult to get in only DJGPP target related 
> patches. About part of others we may perhaps need to wait.

I still have copies in my inbox, if it's djgpp-specific I can approve
them, I'm just really busy.  Remind me every week or two if I don't
get around to them.

For other patches, if it goes two weeks you're entitled to a ping, so
when that happens, mail out a reminder.