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.
Hrrm, you did not serach bery well, did you? I have mentioned this bug several times over the last moth or so already. The taginfo filename bug is present in 2.0.58 and is solved in 2.0.62.1817. All following versions including the 2.5 Release Candidates do not have this bug. If all you want to do is upgrade so you can use the taginfo, then you may install 2.0.51d, which has been reported to work quite well and correctly parses the files for taginfo. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Williams, Tim Sent: den 8 mars 2005 16:37 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Cc: Williams, Tim Subject: [cvsnt] Info in Bug ID: 157 corrupt filenames on STDIN? Hi folks, I am trying to find information on BUG ID:157 reported on CVSNT 2.0.58d : Taginfo script gets corrupted filenames on STDIN. (reported 07Dec2004) I tried looking this up on the bugzilla pages (http://customer.march-hare.com/webtools/bugzilla/) but I can't without an account - and the create an account page is not working. We are trying to build a logging script to capture tagging event information: Name of user, tag, revision and filenames will go to a log file. We can capture all but the revision and filenames (using CVSNT 2.0.5) so we are looking to upgrade. Anyone know if this bug has been addressed in releases after 2.0.58d? Tim SAS Systems Administrator PRA International Charlottesville VA, USA _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs