On Thursday 20 February 2003 10:45 am, Karl Fogel wrote:
> ender <ender@objectrealms.net> writes:
> > ugh.. i should go to sleep.. 'it' above meaning reconstructing a node's
> > path ancestery.
> >
> > so given a file at /A/B/C.txt
> > B is copied over to /D in one txn
> > and C.txt is edited in another txn.
> >
> > C.txt hasn't been copied but using its current path to get contents for
> > annotation with its changed revisions won't work as its been moved. does
> > svn provide any facilities for reconstructing path ancestery? as it is
> > the only solution i can find is an exhaustive search through a node's
> > revisions changed set, checking fs_copied_from till the node no longer
> > exists and then going up to its container or exhausting the rev change
> > set.
>
> Oh, that!
>
> I think issue #1003 contains some changes that will make this possible.
hmm.. i'm not so sure. 1003, fixes a semantic issue with shallow copies and
getting change revisions on the copied node. it also seems to fix some
bookeeping for copies of the node, which will definitely help. but i call
revision_changed explictly with cross_copy_history=1, because i want all the
changed revs for a node to get a handle on each rev's contents to annotate.
out of curosity, how does one go about producing that chart of copy ids that
philip attached to that issue.
-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:58:44 2003