Re: Graphing file changes, copyto, child-nodes and svn obliterate

On 2005-02-15 14:39+1100, Daniel Patterson wrote:
> If it was easy to discover children (new revisions and copies) of a node,
> it would be reasonably fast to do:
>
> 1) svn obliterate some/path
> 2) look back to the earliest ancestor of some/path
> 3) recursively remove child revisions and copies using the
> info described above.
>
> Step 2 is optional (i.e. obliterate only newer stuff). This approach
> (if I've done my reading right) avoids the whole delta-recalculation
> problem with obliterating revisions in the middle of a chain.
>
> Can anyone think of any more uses for "forward" looking information?

At the moment there isn't an easy answer to the question:

  "In which tags/branches is this file presented?"

If we had a child-id, then you could traverse to the beging of the
file, and after that find all children which are ended e.g. under
tags.

BR, Jani

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