From: Brian G. P. <br...@br...> - 2003-04-17 00:55:33
|
statcvs is a really amazing tool, but I've found a bug in how you parse the cvs log files. If the project uses cvs access lists to control access to individual files, stacvs will complain: cvslog line XXXX expected symbolic names: found tyler This may be corrected (worked around) by going through the entire cvslog file and removing all references to the user names on the lines between access list: and symbolic names: Could somebody on the development team take a look at the parsing code for the cvslog file and perhaps devise a fix to skip the user name line(s) between access list: and symbolic names: ? Thanks, - Brian Example of legal cvs log output with user in access list: RCS file: /cvs/gpg/gpg_local_prefs.txt,v Working file: gpg_local_prefs.txt head: 1.2 branch: locks: strict access list: tyler brian symbolic names: V1_1: 1.2 V1_1RC6: 1.2 V1_1RC4: 1.1 V1_1RC3: 1.1 V1_1RC2: 1.1 V1_1RC1: 1.1 Release_V1_0_2: 1.1 V1_0_2: 1.1 V1_0_2_RC3: 1.1 V1_0_2_RC2: 1.1 V1_0_2_RC1: 1.1 Release_1_0: 1.1 keyword substitution: kv total revisions: 2; selected revisions: 2 description: |