Neels J Hofmeyr wrote:
> Just a thought: the 'svn up' will copy all those pristines to the user area.
> If it's faster to copy from the other device than within the same device
> (where the working copy is), copying everything can be faster.
Plus, the 'svn up' will, probably, *validate the checksums* of all pristines
while restoring the working copy. That would slow the whole thing down
* neels makes a mental note of the 'copy-to-user-area' use cases
for the pristine store design.
> Bob Jenkins wrote:
>> Thanks Greg and Philip! Your secret's safe with me :-)
>> -----Original Message-----
>> From: Greg Stein [mailto:gstein_at_gmail.com]
>> Sent: Tuesday, March 02, 2010 4:36 PM
>> To: Bob Jenkins; Philip Martin
>> Cc: dev_at_subversion.apache.org
>> Subject: Re: wc-ng and a reference wc
>> On Tue, Mar 2, 2010 at 11:36, Philip Martin <philip.martin_at_wandisco.com> wrote:
>>> "Bob Jenkins" <rjenkins_at_collab.net> writes:
>>>> they've established (many times with my
>>>> recommendation) a "reference" working copy which is kept up-to-date and
>>>> which individual users copy to create their own working copy. I fully
>>>> appreciated that they would not be able to copy only a sub-tree of a
>>>> working copy moving forward, but I've heard that maybe a working copy
>>>> cannot be moved and therefore copied to another machine. Is that the
>>> 1.7 is going to support centralised metadata in the root of the
>>> working copy and copying that sort of working copy will continue to
>>> work. 1.7 might also support metadata outside the working copy, if it
>>> does it would be optional and copying that sort of working copy would
>>> be more complicated. In either case I expect that copying a subtree
>>> will also be possible, either via some sort of svn-detach script, or
>>> perhaps an 'svn detach' command.
>> To amend: I'm not sure that anybody has set aside time in the 1.7
>> release for doing outside-metadata nor a detach command.
>> Bob: your client should be able to copy the *entire* working copy,
>> from the root (where the metadata is) on downwards. But they will not
>> be able to copy subtrees. You would need to set up separate copy
>> sources for subtrees of interest.
>> It will also be possible to do a "shallow copy", as long as you get
>> that root directory and its metadata. Hmm. In fact, that might be the
>> fastest thing to do for your users:
>> $ mkdir my-working-copy
>> $ cp -r $SOURCE_TREE/.svn my-working-copy/.svn
>> $ cd my-working-copy
>> $ svn up
>> Subversion should then "restore" every file and directory in the
>> working copy from the pristines located in .svn (note that the cp will
>> take a bit, since it is copying all the pristines; but the neat thing
>> is taking advantage of svn's restoring feature, and that we can do it
>> for dirs now, too).
>> Okay. Now don't tell anybody I told you this "monkey with .svn" secret.
Received on 2010-03-05 01:44:35 CET