RE: Checking out an old file, modifying and checking it back in

[Res Pons]

Thanks for the clarification.  I would like to branch one file. Could I just branch the one file or do I need to branch out the whole project because of the 1 file?
 
cvs co -r1.33 fileA
cvs tag -b -r1.33 fileA
 
I'm not clear on the syntax.
 


> Date: Mon, 15 Sep 2008 17:24:30 -0400
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: Re: Checking out an old file, modifying and checking it back in
>
> Res Pons wrote, On 09/15/2008 04:48 PM:
> > Hi all
> >
> > If I check out an old revision of a file, modify,
> > and check it back in,
> > does the revision automatically branch or does it
> > move to the top of the stack as the latest revision?
> >
> > e.g.
> >
> > fileA current revision 1.50
> > fileA old revision to be modified 1.33.
> >
> > I would like to check out fileA rev 1.33,
> > make changes and check it back into CVS.
> > Would it be checked in as 1.33.1 or 1.51 automatically?
> >
>
> neither.
> because you have checked out with a 'sticky tag'[1] of a version, i.e., you did
> cvs checkout -r1.33 fileA
> CVS will not let you commit any changes to that checkout.
> If you want a branch, you need to do a branch tag.
> If you want to replace the contents from rev 1.50 with the contents of 1.33
> into 1.51, (from the link below[1])
> cvs checkout fileA
> #then either
> cvs checkout -p -r1.33 fileA > fileA
> #or IIRC
> cvs update -j1.50 -j1.33 fileA
>
> cvs commit
>
>
>
> [1] http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_4.html#SEC53
>
>
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter

---

See how Windows Mobile brings your life together—at home, work, or on the go. See Now