Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Tue, 29 Apr 2003 09:30:17 +0300, Tuomas Huhtanen <tuomas.huhtanen at vertex.fi> wrote: >0) You have checked out files with some sticky tag (e.g. ct_R1), and are >about to commit the changes made to the files. > >1) Extract the revision number of file to be commited. (e.g 1.1.2.2) >2) Extract the branch number from the revision number (e.g 1.1.2) >3) Force commit to the branch number (1.1.2) >4) Move the tag to the new revision (ct_R1->1.1.2.3) >5) Update the local copy to the moved tag > >This would do it, but not atomically of course. The other thing is that >then I'm bound to specific client of cvs. And third, that would be quite >slow. > Well step 3 at least doesn't make sense - you can't force a commit to a version number that already exists (especially not a branch). Really what you're doing is: 0) Make sure the branch is checked out (which would normally be true anyway) 1) Commit the file (thus creating version 1.1.2.3) 2) Tag -F the file Tony