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:	<10112160620.AA22845@clio.rice.edu>
Subject:	Re: Refresh Proposal
To:	acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date:	Sun, 16 Dec 2001 00:20:51 -0600 (CST)
Cc:	djgpp-workers AT delorie DOT com
In-Reply-To:	<011901c185f8$396af8e0$0102a8c0@acceleron> from "Andrew Cottrell" at Dec 16, 2001 05:08:59 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> I have quickly changed the layout (one type) and added a link to the 2.04
> page. I have uploaded the page to
> http://clio.rice.edu/djgpp/win2k/main_203.htm

Looks better, thanks.

> I wonder if it is a good idea to do one or all or any combination of the
> following:-
> 
> 1) Replace the http://clio.rice.edu/djgpp/win2k/main.htm  with the one
> above.

Cross link maybe.  I wouldn't replace it.  Still a few issues to finish
testing; v2.03 refresh is a check point to get people working while we
finish v2.04.

> 2) Change the Unofficial Win 2K/XP link at www.delorie.com to be the
> "Unnoficial 2.04 site" and add a "Official Win 2K / XP updated DJGPP 2.03
> site" to point to the 2.03 update html page.
> 3) Get DJ to incorporate the 203 update page on his web site.

I wanted to get a few comments and some testing from workers first before
going public.  For example, should we refresh 2.953...

> I would suggest putting the updated 2.03 files in a seperate directory that
> way the are all in the one place.

A good idea.  

- Raw text -