X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Wed, 5 Dec 2001 10:39:24 -0500
Message-Id: <200112051539.fB5FdOd26496@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: sandmann AT clio DOT rice DOT edu
CC: djgpp-workers AT delorie DOT com
In-reply-to: <10112051533.AA16289@clio.rice.edu> (sandmann@clio.rice.edu)
Subject: Re: Refresh update, v2_03_1
References:  <10112051533 DOT AA16289 AT clio DOT rice DOT edu>
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


> > 	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?

The first step is to create the branch.  The above command does that.

Next, check out the branch with "cvs checkout -r v2_03_1 djgpp" in
some empty directory.  If you don't get what you expect, email me and
I'll fix it ;-)

Then, replace/edit/patch the files that need to be patched and commit
them.

I think the trickery needed to set the branch point at the head of
some of the files isn't worth the effort, and it is important to be
able to "cvs get" the patch branch completely.