On Thursday 20 February 2003 11:35 am, cmpilato@collab.net wrote:
> ender <ender@objectrealms.net> writes:
> > On Thursday 20 February 2003 10:45 am, Karl Fogel wrote:
> > > ender <ender@objectrealms.net> writes:
> > > > i'm trying to write a cross-copy annotation of a file, using the
> > > > python bindings. i've dug around in the source, and docs, and don't
> > > > see a good way to do it without an exhaustive search. is there a
> > > > better solution, any tips appreciated.
> > >
> > > svn_log won't cross the copy boundaries for you?
> >
> > not afaics... but svn log doesn't need to cross copy boundaries, it can
> > just get a change revision set (including copy revs) and pick off log
> > /author from the revision props, it doesn't need to get the path. i'd
> > love to be told otherwise ;-)
>
> So... svn_fs_revisions_changed isn't doing the job for you? (Sorry,
> I still don't really understand what you're trying to accomplish.)
i want to produce a line by line annotation/blame showing revision number and
author for changes of a non-binary file node's contents. perhaps a picture is
more clear.
http://objectrealms.net/projects/svn_browser/pics/Annotation.png
to do that i need to get a hold of node's path across all of its
revisions_changed including copies to get ahold of its contents. currently
doing that seems to be problematic, mainly due to expense of iterating
through n*m upper bound of copy checks combinations of n, revision changes to
the node, and m representing the number of hierarchical containers for the
node (though in actuality the number is much less). i was hoping that there
was another mechanism that svn provided for reconstructing a given node's
path across revisions.
-e
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 20 20:56:52 2003