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.
I'm also interested in writing a taginfo script for tracking purposes. I'm eager for a CVS or CVSNT solution (I really don't care about regular CVS). Passing all that information on the command line won't work on Windows -- my build scripts tag the entire repository in one command -- and changing the COMSPEC is not user-friendly. It's questionable whether branch information is coming through (I want to know which branch the tag was added to), and whether filenames that contain spaces pose issues (spaces need to be preceded by a backslash as in loginfo). "Bo Berglund" <bo.berglund at telia.com> wrote in message news:p45aouopt6h75b5vn64oq22gr5vsrki06j at 4ax.com... > I just wonder if the taginfo script will obey the repository prefix > too? > I have tested with 57g and it sends the absolute path instead of > stripping off the repository prefix as the 3rd parameter. In the > WinCvs help the 3rd parameter is said to be the repository, but in > fact what i see is the module. In my case: > Repository prefix: F:/CVSREPO > Repository: /bosse > Module: /CVSMailer/doc > > This is what is sent from taginfo when tagging one file: > Param1 = Test_Tag_4 > Param2 = add > Param3 = F:/CVSREPO/bosse/CVSMailer/doc > Param4 = ToDoList.txt > Param5 = 1.2 > > I am preparing a mailing system for tagging operations in addition to > the loginfo and notify script mailings. > > (Sorry, this was sent to cvsgui instead of cvsnt by mistake...) > > > /Bo > (Bo Berglund, developer in Sweden)