Niels Skou Olsen <nso@manbw.dk> writes:
> Fraser Campbell <fraser@georgetown.wehave.net> writes:
>
>> On Thursday 02 December 2004 04:18, Anthony Metcalf wrote:
>
> [...]
>
>> You're basically after a bandwidth/time efficient way of bringing an export up
>> to date. With a large tree I can see that this would be very useful.
>
> [use diff/patch to keep an export updated]
>
>> diff doesn't tell you the HEAD revision number so you'd have to grab that
>> yourself in another way and update the .exportrev file. You could write a
>> wrapper script to automate the whole thing in a few minutes.
>
> But diff/patch doesn't handle directory tree changes (add, remove, rename
> etc). So this method will never be able to truely keep an export up to
> date.
Come to think of it.. If OP's goal is to keep a huge working copy updated
with the least possible amount of network traffic, then just do the
obvious; make a normal working copy with 'svn co' and keep it updated with
'svn up'. This way you pay up front with a full 'svn co', but you pay only
once. All 'svn up' after this will be as cheap as can be.
Best regards,
Niels
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 8 15:32:38 2004