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.
> My understanding is that viewcvs calls 'cvs rcsfile' directly. I'm not > sure why it would ever parse the RCS files like that. viewcvs does call cvs rcsfile. (Well, that's how I've configured my one to run). There is an option in viewcvs.conf to get it to parse rcs files directly, but IIRC that breaks with cvsnt files... so shouldn't be used. It could be that in the odd place (I'm thinking annotate) that viewcvs is not doing cvs rcsfile even though its been told to do so. I don't know the internals of viewcvs to comment further. cvsgraph, which is called by viewcvs, parses the rcs files directly. So any problems with cvsgraph are to do with cvsgraph only and not viewcvs. > I can move properties (plus stop it appearing when it shouldn't) but it > won't really help parse something like: > > properties > notes:@fixes a bug in the widgets code; to test.@ > to_test:@development team 3@; > > ..there's multiple @ strings plus a semicolon in there.. it doesn't > conform to the 'newphrase' syntax at all. Eeks! > CVSNT is also rather more liberal with what it puts in the files these > days than RCS ever was (relaxed tag naming rules etc.) Sure... but nobody wants viewcvs or cvsgraph to break... but it looks like some burning of the midnight oil is happening and these issues can be resolved. David