probably best off going through the linked tutorials first. On the other, if you're a revision control weenie and pretty much know how SVK works, you might want to skip my rambly ramblings and go to the "Don'ts" section, as it might make entertaining reading :).
At first I found svk to be very confusing and after going through the FAQ links, the blog links, I was able to set it up with great difficulty. For me I had a strange requirement - I wanted to update my local svk branch changes to my sandbox. This was for the obvious reason of not loosing data because of a hard disk crash. Recently I had some filesystem errors (almost a harddisk crash) and I restored my svk repository by creating a new depot in a different filesystem and used the code (its called mirror in svk) from my svn sandbox. smerge algorithm is really cool. I usually merge the trunk to my local branch and merge that, local changes to my svn sandbox. So my svn sandbox always has my local changes + the latest in the trunk. #svk channel at freenode is good if you want to receive a fast response and of course there is a mailing list if you don't find anyone in #svk. Usually I got some of my problems solved hanging out in that channel :) -- Vinu In a world without fences who needs Gates? _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
