X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112080441.AA18762@clio.rice.edu>
Subject: Re: DJGPP 2.03 update
To: djgpp-workers AT delorie DOT com
Date: Fri, 7 Dec 2001 22:41:55 -0600 (CST)
Cc: ams AT ludd DOT luth DOT se
In-Reply-To: <200112080234.DAA18649@father.ludd.luth.se> from "Martin Str|mberg" at Dec 08, 2001 03:34:54 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> Pleaee voice those concerns! (If you don't the bugs will just live on
> longer...).

The bugs I'm talking about are fixed in CVS - but just aren't in the
V2.03 update.  After I did the build we have found a few minor things:

 1) Since djasm didn't get upgraded, the date year has 101 in it :-(
 2) A small fix in dosexec for com file return codes was missed.
 3) Andrew's notice of the 2.02 stub (its that way in cwsdstub too)

It's a matter of balance between getting it perfect and getting it soon.
If the group consensus is we should go another round I'll fix all
the ones we know about.

> Let me take this opportunity to ask if this 2.03 branch (of course
> I've forgotten the exact name) is the one to replace 2.03?

cvs co -r v2_03_1

I have a simple procedure for making any cvs revision currently commited
to be the current v2_03_1 branch for that file.