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

Re: The "follow copy history" initiative

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-04-03 09:00:48 CEST

Branko Čibej <brane@xbc.nu> writes:

> Let me understand this: are you both saying that you'd rather have yet
> another API for full histiry tracking instead of having this one at
> least support the concept, even if the inital implementation doesn't do
> everything?

Here's what I (think I) want:

   svn_error_t *svn_fs_history_next (apr_array_header_t **histories,
                                     svn_fs_history_t *history,
                                     apr_pool_t *pool);

And then I want an RA API and supporting svn_repos_* function which,
given a path, peg revision, and one or two other revisions, uses the
FS history stuff to location the committed-path of path@peg's history
line for each of the other revisions, where forward searching is
instructed to ignore successors that were created by copy. The
additional work of tracking N successors lines and returning a
potentially massive tree of choices to the client app is, in my
opinion, quite premature.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 3 09:28:45 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.