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 firstname.lastname@example.org.
It's the usual reason Bo; it's just more convenient to script that way, especially for updating a version number or something like that. I reworked my scripts to do the update - commit cycle. Thanks chuck Bo Berglund wrote: > On Wed, 02 Aug 2006 13:54:02 -0400, Chuck Kirschman > <Chuck.Kirschman at Nosp_am.bentley.com> wrote: > > >>I just updated to cvsNT 126.96.36.1992, and a command we used to use has >>stopped working. >> >> cvs commit -r BRANCH_1_1 foo.c >> >>Apparently the -r option is no longer available in the commit command. >> How do I do the equivalent commit a file to the tip of a branch in the >>newest versions? > > > The normal procedure for working on a branch is: > > 1) Update the module to the branch: > cvs update -r BRANCH_1_1 > > 2) Edit the file(s) you need to change > > 3) Commit the canges: > cvs commit -m "some log messsage" > > Now the edits are going to the tip of the branch. > > Why do you think that you need to specify the branch to send the edit > to in the first place? Step 1 above can also be applied to single > files if you like and the following commands are still the same.... > > > /Bo Berglund