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: <10112051533.AA16289@clio.rice.edu>
Subject: Refresh update, v2_03_1
To: djgpp-workers AT delorie DOT com
Date: Wed, 5 Dec 2001 09:33:43 -0600 (CST)
Cc: dj AT delorie DOT com
In-Reply-To: <200109261644.f8QGiWe22950@envy.delorie.com> from "DJ Delorie" at Sep 26, 2001 12:44:32 PM
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

Here was DJ's suggestion on what to do with the refresh (about 2 months ago):

> ... We should create a CVS branch for [2.03 update] and commit the 
> patches.  You can get the 2.03 release by checking out the v2_03 branch 
> in CVS, and once checked out, you can use it as the basis for a branch.
> 
> Or, we can branch at the 2.03 point with:
> 
> 	cvs rtag -b -r v2_03 v2_03_1 djgpp

I think the name v2_03_1 is fine.  I haven't read the CVS docs in enough
detail yet to make sure this is exactly what I want to do (since I
then want to cvs update about 18 modules and make 6 point to other
currently existing revisions (which I think I can do).  Comments?
Other suggestions from CVS wizards?

I updated the 4 zips on clio last night to be unix format for the cross 
platform files, updated the .mft and .dsm.