Menu
▾
▴
#54 Generate Stats on Final Product ('annotate')
It would be interesting to see statistics on the 'final'
(current) status of files. Right now, statcvs shows the
cumulative total LoC committed to the repository. In the
scenario where the same developer checked in the same
line of code a million times, their statistics at first glance
would seem to indicate that they did a ton of work on the
project, whereas an analysis of the output of 'cvs annotate'
would show that they contributed only one line.
Just a thought...
Thanks for putting together an awesome project! I wish I
knew (or liked/wanted to know) java and had free time--I'd
give you a hand.
David.Gathright@lasp.colorado.edu
Logged In: YES
user_id=584620
Yes, that would be a useful statistics.
Sadly, it can't be directly calculated from the data we use now. Example:
A has checked in a 5-line file. B changes the file five times, changing one
line each time. That's the information we get from the CVS log. The log
doesn't tell if B has changed the same line five times, or different lines
every time. So B might be responsible for 20% or 100% of the current
status.
One could use the "blame" feature of CVS ("cvs annotate") to get this
information. Downside: User has to perform one more step before he
gets his reports. I'd be more comfortable with this idea if we already had
direct access to the CVS, without requiring the user to check out working
copy/generate log himself.