[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 2206] RFE: Changed #/lines information in svn log -v

From: Kevin Puetz <puetzk_at_puetzk.org>
Date: 2005-02-10 15:01:18 CET

Max Bowsher wrote:

> Adrian Robert wrote:

<snip>

>> But I give up.
>> We've used subversion for a year but will soon switch our project back
>> to CVS since log output is used every day whereas the branching
>> benefits of SVN are more rarely used in our case. We'll miss atomic
>> commits,
> ...
>
> /me mutters something about cutting off your nose to spite your face.
>
> If LOC stats are so useful to you (and I *really* am curious to know why,
> because I genuinely don't understand), why not just write a post-commit
> script which runs "svn diff", calculates the stats, and then appends them
> to the log message?
>
> Max.

Indeed. Or even run diffstat and include that output, which would be an even
nicer view of the information (since the only use I can really see is the
'at a glance' feel for the scope and impact of the change).

It wouldn't even be that hard to use retroactively add them to the log
messages for the existing commits if desired... something like

for i in {1..407}; do
svnlook log -r $i svnroot/ > /tmp/log
svnlook diff -r $i svnroot/ | diffstat >> /tmp/log
svnadmin setlog svnroot -r $i /tmp/log
done;

Or use diffstat -f0 if you really want the hard numbers.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 10 15:04:52 2005

This is an archived mail posted to the Subversion Dev mailing list.