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

[PATCH]: Current work on streamy blame

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-03-25 03:44:29 CET

Sussman asked me to post the current work i have on streamy blame (done
by blaming files from youngest revision to oldest, instead of the other
way around) since it was hoping to be ready for 1.2.

The only file that needs "real" work here is blame-new.c, which is the
implementation of blame in reverse (it obviously needs to be renamed
too :P).

It actually works, as long as you have gnu diff, because instead of
using the internal diff, which i still haven't had time to get working,
it generates "rcs" style diffs which are trivial to parse and blame.
This is not surprising, considering the linevector and other structures
it uses are how i'm told CVS does it.

I attmepted multiple times to reuse the "old" blame's internal diff
handler, with obvious changes to do the opposite of what it does now,
with no success.

The actual client and erver side code for svn, local, and dav to do
handle this stuff is done and working, and is backwards compatible.

If someone could make blame-new work with the internal diff library,
that would be grand :).

Otherwise, i plan on testing and committing the server side and api
changes(IE everything but the call to reverse_blame and the associate
reverse blame functions on the *client* side), because it adds an
argument to svn_ra_get_file_revs, which is new API for 1.2, and thus, if
we don't do it now, we're going to have to add *another* function in
1.3.

Unless someone has a better idea, or believes we should put it all off
*anyway*,etc.

--Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Fri Mar 25 03:46:31 2005

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.