Re: The "follow copy history" initiative

> Anyway. I propose that the API allows searches in any direction, and to
> optionally return a list of paths.

-0 on this. I can see allowing forward search given true rename
tracking, but multiple results for copies is going well beyond the
scope of this function ("where is this file as of that rev?"), even if
we provide that kind of functionality in the future.

>> but "svn_fs_get_node_path" sounds likea simple FS operation.

> There's no reason why it shouldn't _be_ a simple operation. The fact
> that our schema currently makes it a total pain is embarrasing, but
> irrelevant.

When I say "sounds like a simple FS operation," I meant it sounds like
a simple getter function, like svn_fs_node_id. A two-dimensional
search simply can't be that simple; it can be efficient, but it can't
be a simple retrieval operation in any sane implementation. So a word
like "trace" makes more sense than a word like "get".

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 1 22:11:05 2004