Thomas Hruska wrote:
> Jody Shumaker wrote:
[syncing two WCs]
>> You could probably also do this via patches. I don't have much
>> experience with using them, but the basic idea would be to create a
>> patch of your modifications on one pc, transfer it to the other
>> pc, revert th eother pc to a clean working copy, then apply the patch.
> An interesting suggestion and the only one that I've seen that makes
> any sense. Unfortunately, I gave it a try and TSVN choked on a
> directory containing over 15,000 files - of which only a handful are
> actually in the WC. Well, 'choked' may be the wrong word. "Took a
> very long time to return control to the user" is probably more accurate.
> I've also tried using 'svn diff' but that has problems with the binary
> files in my WCs.
If you have binary files, patches won't work for you. Currently
subversion uses a patch file format for the standard "patch" program
which doesn't support binary files (and directory changes). The svn guys
are working on this, but it may take some releases until it's available.
Regarding the response times: They may be related to your former
syncing efforts which may have messed up your file's time stamps.
Try running a cleanup on your WC and see if it gets better.
And regarding your request for a hotsync feature: Since a generally
available feature would *have* to be able to deal with files that are
changed in both WCs, you are right that most probably svn will never
support that, because that's what repositories are for.
You can either work on a WC on a shared drive to avoid the
necessity to sync two WCs or commit your changes in WC1 (maybe to a
"work-in-progress" branch) and update WC2 "the normal way".
I personally don't see a problem with "wasting" revisions - especially
not when doing so in a branch.
If you try to avoid committing and updating, because your connection
to your remote repository is too slow, you may want to have a look
at the svnsync tool that will come with svn 1.4. I have not yet
seen any documentation for it, but it seems to be able to keep a
local copy of a repository in sync with a master repository.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 17 20:30:19 2006