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

Re: git log vs. svn log

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-09-05 21:30:25 CEST

Mattias Engdegård wrote:
> shd@jolt.modeemi.cs.tut.fi (Heikki Orsila) writes:
>
>> pmr.1 | 16 ++++++++++++++--
>> pmr.c | 15 +++++++++++++--
>> 2 files changed, 27 insertions(+), 4 deletions(-)
>
> I wanted this information (added and removed lines) as well, so I wrote
> a script to calculate it as a post-commit hook and save the information
> in a revprop.

FWIW, ViewVC provides a similar script (svndbadmin), but instead drops the
calculated results into a MySQL Bonsai-like database.

Ideally, the Subversion repository would house this type of contextual diff
information so that, for example, we could transmitting full binary diff
streams across the wire when running the links the 'svn blame'. But it
doesn't. The primary storage format in Subversion's repository is a binary
diff that is line-ignorant, and therein lies the primary reason why
Subversion, unlike CVS, ain't so snappy about reporting line-change info.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Wed Sep 5 21:27:18 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.