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

Is 'svn log -g' up to date with current trunk code?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 08 Jan 2008 00:08:06 -0500

Tonight I was wondering who made use of svn_fs_get_mergeinfo_for_tree()
(because I wasn't happy about the fact that it uses a filtering function
instead of just being streamy/callback-y like so many other of our APIs).
The only consumer appears to be 'svn log -g', which is using it to filter
out "branching copies" based on, I think, whether or not the copy resulted
in a mergeinfo diff that matches what you'd expect when doing a copy. Only
problem is, what we now expect when doing a copy is no mergeinfo change at
all, right?

Has this code been updated since we made these changes to the 'copy' behavior?

(My primary goal with this question is that I'd like to know if we can lose
svn_fs_get_mergeinfo_for_tree() before I go and try to implement it anew on
the 'reintegrate' branch.)

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

Received on 2008-01-08 06:08:16 CET

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