On Wed, 2005-11-16 at 14:58 -0800, Jim Blandy wrote:
> But fundamentally, the data in the repository is the only thing that's
> real. If you have an API that can accurately and selectively describe
> what's in the repository, then *by definition* you can do update and
> other hairy things in terms of it. The algorithm can't possibly
> matter, because it's driven by the same data in the end.
I don't quite understand what you're getting at here. We could
implement update in terms of this new svn_repos_replay API, but it would
mean having to download the entire Subversion repository in order to
check out the head revision, and that would be too inefficient.
Our schema is structured so that it's efficient to compare two trees in
such a way as to update a working copy, but I'm not sure if it's
efficient (or even necessarily well-defined) to combine multiple revs
into what looks like a single commit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 17 01:45:52 2005