I want initial revision to be 2.1, not 1.1
"Louis Geronime" <[email protected]> Tue, 26 Jun 2012 16:01:28 -0500
| Newsgroups | gmane.comp.version-control.cvs.tortoisecvs.user |
|---|---|
| Message-ID | <[email protected]> |
Hi; TortoiseCVS version 1.12.5 Concurrent Versions System (CVSNT) 2.5.05 (Gan) Build 3744 We are doing a major upgrade and mgmt want all code (Crystal reports) for the new system to be branded with a new version. Our current CVS system uses the default 1.1 for new files -- which works great. We now want anything checked into the new repository to start at v2.1 -- this sounds fine because Cederqvist says: 4.3 assigning revisions When adding a new file, the second number will always be one and the first number will equal the highest first number. (pg 33) So I: 1) created a test doc, 2) commited it to 2.1. 3) created a second doc 4) commited -- oops it was revision 1.1 5) went to ubuntu, pulled up a command line cvs 6) from ubuntu shell, commited a third doc -- it was revision 2.1 Is there something I can do to change CVSNT's behavior? Is there a different CVS client I can run Tortoise with that supports the revisions? how? hints? I noticed that CVSNT... you must now pay a distribution fee to obtain the Community Edition of CVSNT. I think this is an issue with CVSNT but hope* someone has a solutiion... thanks! -Louis ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/