Hi, I think it has been solved by updating cvs path. The old PATH pointed to the cvs version 1.11.5. The new one points to the expected 2.0.4. My project now seems to be working fine. I can checkout and commit different versions. When I select Branch... menuitem from TortoiceCVS menu TortoiceCVS runs cvs -b -c v1-1-1.... Should it add the release as well?
-- Csaba > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 21, 2003 3:52 PM > To: [EMAIL PROTECTED] > Subject: Re: How to separate stable and unstable versions > > > Egy�d Csaba wrote: > > > > Hi Matt, > > I've made a new branch for my stable version and I'd like > to continoue the > > development on the 'main trunk' as the doc mentions it. My > problem is that > > commiting the changes cvs says the following: > > > -------------------------------------------------------------- > -------------- > > ------------------------------------------ > > cvs commit: sticky tag `ver1-1-1-2' for file > `source/MainForm.dfm' is not a > > branch > > You created a tag, not a branch. It is good to use a tag to "anchor" a > branch, but now you need to create a branch with the '-b' > option to 'cvs > tag'. The following would create a branch based on 'ver1-1-1-2': > > cvs tag -b -r ver1-1-1-2 ver1-1-1-2-branch > > Note that it may be more useful to name the branch based on a > higher-level rev, like 1-1-1 vs. 1-1-1-2; you could then tag > the branch > as 1-1-1-x if you wanted to make a bug fix release. Adjust the above > accordingly. > > -Matt > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.528 / Virus Database: 324 - Release Date: 2003. 10. 16. > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.528 / Virus Database: 324 - Release Date: 2003. 10. 16. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
