Re: Subversion, decentralized version control, and the future.

Karl Fogel wrote:
> The working copy should really be a repository, even if
> it's not always going to store all the history available on the server
> side (with some projects, you really can't, it's too big).

Strangely enough, this is precisely how SVK manages it. But, if
Subversion is still going to support moving a subtree out of a WC and
still have it work, literally the working copy may need to be an entire
tree of [loosely coupled] repositories. SVK has a central (local)
repository, so that isn't an issue, but it seems like there has always
be a strong current in Subversion proper against centralized file
storage (especially in "hidden" directories of various platform-specific
species).

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org