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.
As I stated this was a copy of a ViewCvs list mail because I thought that the CVSNT list would have better possibilities of answering. I will forward your reply to the ViewCvs list and hopefully the developers there can fix this. They have already swiched from RCS to using the cvs.exe for parsing the RCS files, now someone also needs to check up on how cvsgraph is called. If we are lucky then cvsgraph does not call RCS by itself but rather use suff sent in by the ViewCvs system. If we are unlucky then the cvsgraph developer has to be activated and switch from RCS to cvs.exe too. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Tony Hoyle Sent: den 2 april 2004 11:51 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: CVSNT 2.0.34 puts extra info in RCS files that CVSGraphdoes not like... On Thu, 01 Apr 2004 19:43:22 +0200, Bo Berglund <bo.berglund at telia.com> wrote: >This is a copy of an email that was posted on the ViewCvs mailing >list. >I thought that I should re-post it here in order to have Tony or >someone else look at it and see if anything can be done about it. >I have looked at some of my RCS files and indeed there is no @ >characters enclosing the committing user. >/Bo The @ characters are necessary when then username contains non-alphanumeric tokens. It's actually an error in the original RCS specs - they treated the author name as a token which fails horribly if the name has a space or several other characters in it (@, ;, a few others). Even in the 'old' CVS if you had a username with spaces you'd get a broken RCS file which CVS could read but RCS couldn't, so there's no real change to the behaviour in that sense... CVSNT tries to avoid using the @ bracketing if your name is also a valid token. Really you must use the RCS wrappers with CVSNT repositories. These handle such things (and more major changes, like binary deltas) transparently. Tony _______________________________________________ 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