RE: [Statcvs-users] Cumulative statistics for all modules in cvs repository

[Michael B. <mic...@tr...>]

Thanks for pointing me in the right direction.

The command that worked on my system was "cvs co ."

Then log worked for entire repository.  Now have statistics for all
projects for all developers.

-----Original Message-----
From: Richard Cyganiak [mailto:ri...@cy...]=20
Sent: Monday, March 06, 2006 9:49 AM
To: Michael Blake
Cc: sta...@li...
Subject: Re: [Statcvs-users] Cumulative statistics for all modules in
cvs repository

Hi Michael,

This is a bit of a hack and I didn't try it myself, but reportedly =20
you can checkout the root module ("cvs co /") and run StatCVS on that.

Best,
Richard


On 6 Mar 2006, at 15:32, Michael Blake wrote:

> Has there been any effort to aggregate the data across all modules =20
> in a repository?
>
>
>
> We have a single cvs repository with 94 projects.  Each project =20
> gets worked on at some time during the year depending on the =20
> release schedule.  Developers hop from project to project over the =20
> course of the year, so the statistics are useful, but can't really =20
> be summarized for the year unless statcvs is run in each one and =20
> then totals are manually calculated (yuck).
>
>
>
> Right now I have statcvs set up to run a 30 day, 60 day, 90 day, =20
> and ytd for all the projects at midnight, and it works nicely with =20
> the ViewCVS server.
>
>
>
> The cvs update, log generation and transfer to the intranet web =20
> server takes about 25 minutes.
>
>