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: <10201211640.AA21306@clio.rice.edu>
Subject: V2.03 refresh details
To: djgpp-workers AT delorie DOT com (DJGPP developers)
Date: Mon, 21 Jan 2002 10:40:01 -0600 (CST)
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

We need to decide what to do with suggested V2.03 refresh changes.

V2.03 refresh has been on Simtel for a couple of weeks.  No questions
about Win2K/XP problems since then on newsgroup :-)  I have not sent
out an announcement about this (but it does say it on the refresh web
page).  I have been too busy to deal with the last minute flurry potential 
changes.  I am going to have a very busy month, so I can't do a full 
rebuild/beta of everything.  But I would like opinions on the options.
The things I have on my list:

1) Update sys/djtypes va_list (to allow GCC 3.x to build).  Looks low risk.
   Could replace file in distributions.

2) I've noticed readme.1st has lots of CVS updates and I didn't update
   it in the refresh.  Seems really low risk :-)  Adding information
   on Win2K and XP setup seems to make lots of sense.
   
3) stat win2k device bit patch.  Changes libc.a, source distributions, 
   really should update binaries too.  Lots of work, not noticed in
   months of testing until after release.  Defer (probably til 2.04?)

Options:

1) Announce v2.03 refresh, don't do anything.
2) Replace sys/djtypes.h and readme.1st in distribution, then 
   announce v2.03 refresh.