You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(19) |
Jun
(1) |
Jul
(10) |
Aug
(3) |
Sep
(10) |
Oct
(2) |
Nov
(16) |
Dec
(6) |
2004 |
Jan
(13) |
Feb
(2) |
Mar
(15) |
Apr
(8) |
May
(5) |
Jun
(1) |
Jul
(3) |
Aug
(5) |
Sep
|
Oct
(38) |
Nov
|
Dec
(7) |
2005 |
Jan
(16) |
Feb
(8) |
Mar
(34) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
(18) |
Dec
(10) |
2006 |
Jan
(1) |
Feb
(1) |
Mar
(4) |
Apr
|
May
|
Jun
(20) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(5) |
Nov
(22) |
Dec
(10) |
2007 |
Jan
(16) |
Feb
(12) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(6) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Robin G. <rg...@bl...> - 2005-01-02 17:45:48
|
Richard Cyganiak wrote: >You are right. Could you please add this to the bug tracker? >http://sourceforge.net/tracker/?group_id=57558&atid=484569 Will do. Also, when I was trying -cvsweb option, I passed it: -cvsweb http://cvs.blackfin.uclinux.org/cgi-bin/cvsweb.cgi And statcvs passed me back urls formed like: http://cvs.blackfin.uclinux.org/cgi-bin/cvsweb.cgi/u-boot_1.1.1/cpu/bf533/interrupts.c.diff?r1=1.15&r2=1.16&f=h However, it needs to have a cvsroot= in it, like so: http://cvs.blackfin.uclinux.org/cgi-bin/cvsweb.cgi/u-boot_1.1.1/cpu/bf533/interrupts.c.diff?cvsroot=uboot533&r1=1.15&r2=1.16&f=h Am I passing the wrong parameter to cvsweb? > > 3) How are the user statistics -> modules -> pie chart created? What > > signifies when something should be kept together? or split apart? > >I'd have to look at the code to say for sure. If I remember correctly, >it works like this: By default, everything is kept separately. If all >of a directory's subdirectories taken together are less than some >threshold, then they will be lumped together. The intention was to >avoid lots of tiny pie slices, but it doesn't work very well, and a >case could be made for dropping these charts from the report >altogether. I actually think this is a great idea, but could be sorted by sub-directory/file and things are added until they hit some threshold. What happens on my logs is that 80% is grouped to "other". Check: http://statcvs.blackfin.uclinux.org/uboot533/user_lgsoft.html http://statcvs.blackfin.uclinux.org/gcc3/user_bernds.html We are doing a linux kernel port to the Blackfin processor, and our log for the kernel cvs is 65Meg. Maybe some note about the -mx java option in the doc would be nice? I also noticed that while running on these large logs, it consumes _very_ large amounts of CPU resources (while running, it takes 96-99% of available CPU). Other than 'nice' any suggestions? Thanks -Robin |
From: Richard C. <ri...@cy...> - 2005-01-02 15:17:02
|
Hi Robin, Am 02.01.2005 um 06:32 schrieb Robin Getz: > 1) When rerunning this (as a nightly or weekly cron) - is it necessary > to delete everything in the existing directory? (I didn't see any > recommendations about running as a cron in the manual) No, deleting the old reports is not necessary, but neither does it improve anything. All old files will be overwritten. > 2) I found a "bad" file in one of the repositories named '*?'. this > Made the log something like: <snip> > Why the file is there - I don't know (and will be removing it soon) > but wouldn't it be better to create the rest of the stats without one > file, than stop working all together - if only one filename is bad? You are right. Could you please add this to the bug tracker? http://sourceforge.net/tracker/?group_id=57558&atid=484569 > 3) How are the user statistics -> modules -> pie chart created? What > signifies when something should be kept together? or split apart? I'd have to look at the code to say for sure. If I remember correctly, it works like this: By default, everything is kept separately. If all of a directory's subdirectories taken together are less than some threshold, then they will be lumped together. The intention was to avoid lots of tiny pie slices, but it doesn't work very well, and a case could be made for dropping these charts from the report altogether. Cheers, Richard |
From: Robin G. <rg...@bl...> - 2005-01-02 05:32:32
|
Hi - I just was installing this in a few cvs respositories I have set up, and it is working very well - but (as always) had a few questions. 1) When rerunning this (as a nightly or weekly cron) - is it necessary to delete everything in the existing directory? (I didn't see any recommendations about running as a cron in the manual) 2) I found a "bad" file in one of the repositories named '*?'. this Made the log something like: ---snip---- RCS file: /cvsroot/uboot533/u-boot_1.1.1/disk/*^M,v Working file: u-boot_1.1.1/disk/*^M head: 1.1 branch: 1.1.1 ---snip---- On this, statcvs complains: ---------- Logfile parsing failed. line 58478: expected 'Working file: ' but found ',v' ----------- Why the file is there - I don't know (and will be removing it soon) but wouldn't it be better to create the rest of the stats without one file, than stop working all together - if only one filename is bad? 3) How are the user statistics -> modules -> pie chart created? What signifies when something should be kept together? or split apart? Thanks - very cool application -Robin |
From: Jukka U. <juk...@dn...> - 2004-12-14 20:52:11
|
Steffen Pingel wrote: > Hi, > > I merged the patch that adds support for symbolic names and parsing of > CVS/Entries files to check the working revision for loc counting. I > tagged the repository before applying the patch > (symbolic_names-1-before-merge) and after merging it ( > symbolic_names-1-merge). That way the delta can be removed easily if > needed. > > Currently the symbolic names are displayed in the global and the authors > loc chart. It might prove useful to add support for filtering symbolic > names (tags) through regular expressions like StatCvs-XML has. Usually > it is not desired to have all tags in the chart (i.e. branch/patch merge > tags). Some people might even want to turn tags completly. > > Please let me know, if there are any problems with the patch. > I checked out latest and seems there are something missing in test-src. I got classes in src to compled but with test-src, i got lot of errors, missing classes, missing methods etc. - Jukka - |
From: Steffen P. <ste...@gm...> - 2004-12-14 13:44:20
|
Hi, I merged the patch that adds support for symbolic names and parsing of CVS/Entries files to check the working revision for loc counting. I tagged the repository before applying the patch (symbolic_names-1-before-merge) and after merging it ( symbolic_names-1-merge). That way the delta can be removed easily if needed. Currently the symbolic names are displayed in the global and the authors loc chart. It might prove useful to add support for filtering symbolic names (tags) through regular expressions like StatCvs-XML has. Usually it is not desired to have all tags in the chart (i.e. branch/patch merge tags). Some people might even want to turn tags completly. Please let me know, if there are any problems with the patch. Steffen PS: Richard, could you take a look at this bug report: http://sourceforge.net/tracker/index.php?func=detail&aid=1058363&group_id=57558&atid=484569 I added the missing backslash (which caused a ParseException when I was trying to run StatCvs as described in the report), so you can close the report. |
From: Richard C. <ri...@cy...> - 2004-12-09 20:51:40
|
Am 09.12.2004 um 20:59 schrieb Steffen Pingel: > I have merged the model changes into StatCvs-XML, so it should be > pretty easy > to create a new patch that smoothly merges into StatCvs. > > Richard, would you like me to post an updated version of the patch to > the > SourceForge patch tracker? That would be great! Maybe you could even take a stab at merging the patch into StatCVS? Richard |
From: Steffen P. <ste...@gm...> - 2004-12-09 19:59:20
|
Hi, > Any status update on displaying Tag information in the SataCVS display, per > the patch that was talked about a while back on this list? I have merged the model changes into StatCvs-XML, so it should be pretty easy to create a new patch that smoothly merges into StatCvs. Richard, would you like me to post an updated version of the patch to the SourceForge patch tracker? Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Brian G. P. <br...@br...> - 2004-12-09 19:43:19
|
Richard (or other developers) Any status update on displaying Tag information in the SataCVS display, per the patch that was talked about a while back on this list? Thanks, - Brian |
From: Richard C. <ri...@cy...> - 2004-12-09 18:16:52
|
Hi Vinoth, > cvs log: unknown method in CVSroot: > :sspi:abcd@:2401/repositories/abc-def Note the :sspi: part. That's the access method which must be used to access your repository. Looks like your CVS client doesn't support that method. It's not a standard method like :pserver:. I don't know which clients support it. Maybe CVSNT? I think you should ask the administrator of the repository. Ask him how to access the repository with a CVS command line client. Cheers, Richard |
From: Vinoth <vh...@gf...> - 2004-12-09 15:25:07
|
I've used the statcvs-0.2.2, 1. I check out the module in eg: e:\project\v1.0>=20 2. From the command prompt I changed into that directory and give = e:\project\v1.0> cvs log > impl.log as show in statcvs manual 3. But i got the below exception cvs log: unknown method in CVSroot: = :sspi:abcd@:2401/repositories/abc-def cvs [log aborted]: Bad CVSROOT. 4. But the same is working for another project which is in :Pserver = protocol(Windows Authentication) What should I do to over come this problem. thanx in Advance |
From: Richard C. <ri...@cy...> - 2004-10-27 10:41:15
|
Hi, if you want to create a log for your project, go into the directory =20 where you have checked out your working copy, and type "cvs log". If =20 everything works, lots of text will scroll past, looking like the =20 snippet I've given below. If it works, type "cvs log > logfile.log" to save the log into a file. =20= You can open "logfile.log" in a text editor. Its contents should look =20= like the stuff below. Then you are ready to run StatCVS. Hope that helps, Richard Example CVS log snippet follows: RCS file: /cvsroot/ng4j/ng4j/.cvsignore,v Working file: .cvsignore head: 1.5 branch: locks: strict access list: symbolic names: V0: 1.1.1.1 NO_VENDOR: 1.1.1 keyword substitution: kv total revisions: 6; selected revisions: 6 description: ---------------------------- revision 1.5 date: 2004/10/23 13:18:51; author: cyganiak; state: Exp; lines: +0 -1 Revert last change, didn't fix problem ---------------------------- revision 1.4 date: 2004/10/23 13:15:12; author: cyganiak; state: Exp; lines: +1 -0 Re-organizing .cvsignore, I hope this will fix an Eclipse problem ---------------------------- revision 1.3 date: 2004/09/13 16:01:21; author: cyganiak; state: Exp; lines: +1 -0 New zip task for buildfile ---------------------------- revision 1.2 date: 2004/09/13 15:27:38; author: cyganiak; state: Exp; lines: +1 -0 Added jar task to buildfile ---------------------------- revision 1.1 date: 2004/09/13 14:37:23; author: cyganiak; state: Exp; branches: 1.1.1; Initial revision ---------------------------- revision 1.1.1.1 date: 2004/09/13 14:37:23; author: cyganiak; state: Exp; lines: +0 -0 Initial import of code and tests written so far =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 =3D=3D=3D=3D=3D RCS file: /cvsroot/ng4j/ng4j/build.xml,v Working file: build.xml head: 1.8 branch: Am 27.10.2004 um 09:53 schrieb cheng ming: > Sir,Hi! > I want to need some help about cvs log file. > Because when I run StatCVS,I got error: > Logfile parsing failed. > Empty logfile! > So,would you please give me an example for cvs log file? > Thanks for your help! > Best regards > ChengMing > > _________________________________________________________________ > =CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE= =CF=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick > _______________________________________________ > Statcvs-users mailing list > Sta...@li... > https://lists.sourceforge.net/lists/listinfo/statcvs-users > |
From: cheng m. <che...@ho...> - 2004-10-27 07:54:48
|
Sir,Hi! I want to need some help about cvs log file. Because when I run StatCVS,I got error: Logfile parsing failed. Empty logfile! So,would you please give me an example for cvs log file? Thanks for your help! Best regards ChengMing _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com |
From: Scott F. <sc...@at...> - 2004-10-26 03:01:50
|
I can email it to you, or put it up on an FTP site if you want. Also includes the ability to ignore number of calculated lines, and therefore not require a local repository. Basically we use it for more than just lines of code - we use the object model in memory. So we don't calculate lines of code for branches, we just navigate the object model. I'm not sure how generally useful it is, and we haven't had a chance to merge it back in to the main trunk, but if someone is interested (or interested in putting it back in to the main trunk), then let me know. Cheers, Scott On Mon, Oct 25, 2004 at 03:59:01PM +0200, Richard Cyganiak wrote: > Scott, > > Am 25.10.2004 um 15:09 schrieb Scott Farquhar: > >Indeed, we use our own version of StatCVS to parse log files, and we > >use > >that integration to integrate CVS with JIRA: > > > > > >http://www.atlassian.com/software/jira/docs/latest/ > >cvs_integration.html > > Looks very nice. Having issue tracking, CVS logs and ViewCVS tightly > integrated seems like a good and useful thing to me. > > >It even handles branches :) > > What can it do? Just filter for a single branch, or more? > > What do I have to do to get the source? > > Best, > Richard > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Statcvs-users mailing list > Sta...@li... > https://lists.sourceforge.net/lists/listinfo/statcvs-users |
From: Richard C. <ri...@cy...> - 2004-10-25 13:59:08
|
Scott, Am 25.10.2004 um 15:09 schrieb Scott Farquhar: > Indeed, we use our own version of StatCVS to parse log files, and we > use > that integration to integrate CVS with JIRA: > > > http://www.atlassian.com/software/jira/docs/latest/ > cvs_integration.html Looks very nice. Having issue tracking, CVS logs and ViewCVS tightly integrated seems like a good and useful thing to me. > It even handles branches :) What can it do? Just filter for a single branch, or more? What do I have to do to get the source? Best, Richard |
From: Scott F. <sc...@at...> - 2004-10-25 13:09:17
|
On Fri, Oct 15, 2004 at 07:58:21PM +0200, Richard Cyganiak wrote: > Brian has already pointed out that CVS comments are often used to refer > to bug numbers from bug tracking software. These CVS comments might be > used to analyse # of bugs fixed per developer, time of bugfixes and > similar things. > > On a related note: You have already mined SourceForge.net for CVS data. > SourceForge also provides bug trackers for projects, similar to those > mentioned by Brian. You might use screen scraping technology to extract > data about bugs from these trackers (date opened, date closed, > developers involved). CVS comments might be used to cross-correlate > this data with data from the CVS. Indeed, we use our own version of StatCVS to parse log files, and we use that integration to integrate CVS with JIRA: http://www.atlassian.com/software/jira/docs/latest/cvs_integration.html It even handles branches :) Cheers, Scott |
From: Richard C. <ri...@cy...> - 2004-10-20 10:29:59
|
Brian, good news. Am 19.10.2004 um 13:40 schrieb Brian G. Peterson: > StatCVS-XML shows tagged versions of code as labeled verical dotted=20 > lines. > This functionality is the only feature that seems even remotely=20 > compelling > about StatCVS-XML. Otherwise, I prefer the completeness of StatCVS,=20= > and have > used StatCVS for a long time. In the defense of StatCvs-XML it must be said that it also features the=20= Maven plugin, which is its real raison d'=EAtre. And they have a much better release policy ;-) > Richard, any chance you might be convinced to take a look at how they=20= > are > parsing out and rendering the version tags? Steffen has prepared a patch for StatCVS containing the changes to the=20= parser. It has been sitting in the Patches section of the SourceForge=20 site for months. Now with 0.2 out of the door it's the top item on my=20 StatCVS to-do list. Chances are that this feature will show up in=20 StatCVS within the next couple of weeks. That's also a stepping stone to support for branches, which seems to be=20= the #1 feature request these days. Best, Richard= |
From: Brian G. P. <br...@br...> - 2004-10-19 11:40:47
|
I've recently evaluated StatCVS-XML, and there si only on e feature that I really hope Richard and the main StatCVS team will consider merging into the main StatCVS from the StatCVS-XML fork. StatCVS-XML shows tagged versions of code as labeled verical dotted lines. This functionality is the only feature that seems even remotely compelling about StatCVS-XML. Otherwise, I prefer the completeness of StatCVS, and have used StatCVS for a long time. Richard, any chance you might be convinced to take a look at how they are parsing out and rendering the version tags? Thanks, - Brian |
From: Brian G. P. <br...@br...> - 2004-10-19 11:30:46
|
On Tuesday 19 October 2004 02:23 am, llchen wrote: > when I type 'java -jar statcvs-xml-0.9.4-full.jar' StatCVS-XML is a different project from StatCVS. The StatCVS-XML project page is here: http://statcvs-xml.berlios.de/ and the mailing list info is here: http://statcvs-xml.berlios.de/mail-lists.html Regards, - Brian |
From: <tva...@ta...> - 2004-10-19 09:21:33
|
Hi. > when I type 'java -jar statcvs-xml-0.9.4-full.jar' > > in screen shows > Revision of cm_crestplan.log doed not match expected revision > > why? > 1) statcvs-xml has its own mailinglist (see CC). 2) this message is just an information, it occurs if your log is not up to date. Please rerun cvs log > cvs.log Tammo |
From: llchen <ll...@me...> - 2004-10-19 07:21:54
|
d2hlbiAgSSB0eXBlICdqYXZhIC1qYXIgc3RhdGN2cy14bWwtMC45LjQtZnVsbC5qYXInDQoNCmlu IHNjcmVlbiBzaG93cw0KUmV2aXNpb24gb2YgY21fY3Jlc3RwbGFuLmxvZyBkb2VkIG5vdCBtYXRj aCBleHBlY3RlZCByZXZpc2lvbg0KDQp3aHk/DQo= |
From: Richard C. <ri...@cy...> - 2004-10-16 12:13:36
|
Hi Simon, Am 15.10.2004 um 23:55 schrieb Simon Josefsson: > A feature request: make it possible to "embed" the HTML output. One > solution that I believe would be sufficient for me would be to have > two new parameters -tophtml and -bottomhtml, that specified two files. > The contents of those files would be added to the top and bottom, > respectively, of each generated HTML file. The generated output would > have to remove the <html>, <head> and initial <body> stuff, also. I'm a bit opposed to this. Sounds useful, but when we add this, there will soon be requests for customizable <title>, different headers for different types of report pages. I believe that if we want customizable output, then it should be *really* customizable, not just a minimal solution that will not be sufficient in many cases. I'd like to understand why stand-alone reports are not good enough. What are the requirements for the customized reports? Integration with corporate design? Integration in site navigation? Additional information/explanations on every page? That's a question to everyone who wishes for better customizability (it's not the first time the subject comes up). > I noticed StatCVS-XML, but I didn't understand how they embedded their > pages, nor what the difference compared to StatCVS was. But at least > StatCVS-XML used a lot more memory. :-) StatCvs-XML generates XML output and uses XSLT stylesheets to generate either HTML or Maven doc files. That's a very flexible approach. I don't know how much effort it would be to adapt their XSLT stylesheets for your needs, but this would be a way to achieve your goals. Best, Richard |
From: Brian G. P. <br...@br...> - 2004-10-16 11:27:38
|
On Friday 15 October 2004 04:55 pm, Simon Josefsson wrote: > A feature request: make it possible to "embed" the HTML output. One > solution that I believe would be sufficient for me would be to have > two new parameters -tophtml and -bottomhtml, that specified two files. > The contents of those files would be added to the top and bottom, > respectively, of each generated HTML file. The generated output would > have to remove the <html>, <head> and initial <body> stuff, also. > > I noticed StatCVS-XML, but I didn't understand how they embedded their > pages, nor what the difference compared to StatCVS was. But at least > StatCVS-XML used a lot more memory. :-) Load the StatCVS pages in a frameset. You can also change the colors by modifying the statcvs.css stylesheet. Not perfect, but it will work. Regards, - Brian |
From: Simon J. <ja...@ex...> - 2004-10-15 21:55:43
|
A feature request: make it possible to "embed" the HTML output. One solution that I believe would be sufficient for me would be to have two new parameters -tophtml and -bottomhtml, that specified two files. The contents of those files would be added to the top and bottom, respectively, of each generated HTML file. The generated output would have to remove the <html>, <head> and initial <body> stuff, also. I noticed StatCVS-XML, but I didn't understand how they embedded their pages, nor what the difference compared to StatCVS was. But at least StatCVS-XML used a lot more memory. :-) Thanks. |
From: Simon J. <ja...@ex...> - 2004-10-15 20:49:47
|
Richard Cyganiak <ri...@cy...> writes: > Am 15.10.2004 um 22:21 schrieb Simon Josefsson: >> Hello, it works fine now. I think I may have been using an older JVM >> before. Thanks for the help, I'm now using StatCVS for Libidn: >> >> http://josefsson.org/libidn/statcvs/ >> >> And will use it for GnuTLS, GNU GSS/Shishi/SASL as well, unless I run >> into some problem. > > Cool! > > The fix is committed to CVS. Thanks! Btw, the other pages I mentioned are: http://josefsson.org/gsasl/statcvs/ http://josefsson.org/gnutls/statcvs/ http://josefsson.org/gss/statcvs/ http://josefsson.org/shishi/statcvs/ Quite interesting reading. |
From: Richard C. <ri...@cy...> - 2004-10-15 20:33:53
|
Am 15.10.2004 um 22:21 schrieb Simon Josefsson: > Hello, it works fine now. I think I may have been using an older JVM > before. Thanks for the help, I'm now using StatCVS for Libidn: > > http://josefsson.org/libidn/statcvs/ > > And will use it for GnuTLS, GNU GSS/Shishi/SASL as well, unless I run > into some problem. Cool! The fix is committed to CVS. |