Brad Appleton wrote:
>
> But if one chose a more physical (file-system centric) middle point of
> granularity, then a subtree of the repository, rooted at a particular
> directory, might be a good candidate. The current externals mechanism
> allows mapping to something that looks like this, tho its not quite the
> same thing.
I had the same thoughts a while ago as well - this seems a reasonable
point of view.
> This would mean that revisions might be repo-wide, or could be
> narrowed/pared down to a subtree. Recursion would be interesting to
> handle, amd som ekind of inheritance mechanism might need to be
> specified as to whether or not a revision of a subtree would "percolate"
> up to its its containing parent or not, and when/if the parent version
> would simply map to an assembly of "sub versions" (versions of subtrees)
>
> Then again, maybe the better way to handle it (particularly with
> recursion) is the virtual repository of repositories model.
- thomas beale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 12 18:36:54 2005