[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS diffs
Mark D. Baushke
Re: CVS diffs
Fri, 09 May 2003 03:05:26 -0700
I believe you will find the 'cvs log' command to be very useful.
Included for each version is the 'lines: +n -m' which is a count of the
lines that have been added and removed from the previous version of the
file. The same line has the date: and author: fields.
All that said, you may find the 'CVS Statistics Generator' does most of
what you need:
It generates some fairly nice statistics.
Pitfield, Nickolas <address@hidden> writes:
> I've been asked to provide some metrics on code churn for one of our
> projects - the source of which resides in CVS: the server is on SuSE 7.2 box
> and the clients are on Solaris 8 (cvs v1.10) and Win2K (wincvs 1.3).
> What I've been asked to provide is the weekly code churn (number of lines
> changed/added/deleted as a percentage of total code size). This is required
> from the head 5 months ago until a particular release was branched, and then
> for that particular branch to the present).
> I'm relatively new to CVS. I can figure out the date/branch-related stuff,
> but am not sure about the diffing at all. I can see nothing in Cederqvist
> about diffs of this metric-gathering nature, only diffs for
> patch-application purposes - in fact all the diff variants I'm aware of have
> no metrics gathering stuff that I've seen. Are there any options to get such
> info out of cvs diff/rdiff, or am I going to have to hack the diff output ?
> Not being Python literate I'll be writing a bash/ksh script for this.
> Nick Pitfield
> Configuration Management Engineer
> T: +44 (0)20 7348 1569 E: address@hidden
> MetaSolv Software Limited
> Avon House, Kensington Village, Avonmore Road, London W14 8TS
> T: +44 (0)20 7348 1500 F: +44 (0)20 7348 1501
> Info-cvs mailing list
- CVS diffs, Pitfield, Nickolas, 2003/05/09
- Re: CVS diffs,
Mark D. Baushke <=