Shawn, TortoiseCVS has a built in CVSNT client - it always works best with CVSNT.
Please ask on the CVSNT forum: http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt or news://news.cvsnt.org/support.cvsnt Or read the manual (commit id's): http://www.cvsnt.org/manual/ Basically a commit id can be used anywhere a tag is usually used, just use the commit id syntax. Regards, Arthur > -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > org] On Behalf Of Shawn Matlock > Sent: Wednesday, 29 August 2007 4:26 AM > To: [email protected] > Subject: RE: automated rollback tag > > > I (finally) created a CVSNT server instance on my pc to test this. I > normally use TortoiseCVS as the client. Can I use it for this? If not, > what are my choices? In either case, where can I find out how > to do it? > > (If this isn't the right forum to ask, please point me in the right > direction.) > > Thank you, > Shawn > > > -----Original Message----- > > From: Arthur Barrett [mailto:[EMAIL PROTECTED] > > Sent: Thursday, July 19, 2007 8:36 AM > > To: Shawn Matlock; [email protected] > > Subject: RE: automated rollback tag > > > > Shawn, > > > > > CVS version 1.11.17 > > > > > > I'm trying to work out a method to create a rollback tag. > > > > > . > > . > > . > > > > > > My solution is to create a Perl script: > > > 1. check out the RC3 tag > > > 2. *individually* update each file to RELEASE <-- slow/painful > > > 3. tag all the working copy with RC3_rollback > > > > > > Is there a better solution to this? > > > > Use CVSNT (Linux/Unix/Mac/Win, GPL just like CVS) for each commit it > > automatically creates a "commit id" and you can also specify user > defined > > change sets (eg: job numbers or bug numbers) and > update/merge based on > the > > user defined bug number or the commit id. > > > > If you want "modern CM" features like change sets and > mergepoints and > > access control lists then I suggest you use CVSNT - one of > the reasons > > there are "two" CVS projects is so CVSNT can implement all this new > > functionality. > > > > Regards, > > > > > > Arthur Barrett > > >
