On 1/12/2006 7:43 AM, Peter Valdemar Mørch wrote:
> Duncan Murdoch murdoch-at-stats.uwo.ca |Lists| wrote:
>
>>svk (http://svk.elixus.org/) is a project based on the svn source code,
>>that allows you to mirror the repository and work with it when you don't
>>have a connection to the real one.
>
>
> No, it is not based on the svn source code, it builds on top of svn. It
> uses svn and svn perl hooks behind the scenes. Not a separate svn code base.
>
>
>>I don't know how it handles sync'ing
>>when the connection comes back up.
>
>
> It does nice merges! svk rocks!
>
>
>>The hard problem is what to do if you commit some changes at home, then
>>forget to sync with work, and commit some changes there. With your
>>scheme (copying the whole repo on a USB key), one set of changes would
>>be lost completely unless you did some sort of tedious manual merge. I
>>don't know the details of what svk does.
>
>
> Copying the whole repo sounds dangerous. Then there will be ambiguity as
> to what "revision 45" is.
Thanks for the additional details about svk. This is a bit off-topic
for this list, but how does it handle the ambiguity about "revision 45"?
Perhaps a little bit less off-topic, are there any plans to bring the
same repo-mirroring ideas into svn?
Duncan Murdoch
>
> svn also handles merge history. Tres cool!
>
>
>>I think my repository is too valuable to trust it to svk, because I
>>don't see the level of community support for it that I see with svn.
>
>
> There need be no changes made to configuration of software running the
> svn repository "at work". svk will work seemlessly with any subversion
> repository. Thats the beauty.
>
> I'd definitely go for svk. Its made for what you ask. My $0.02 anyway.
>
> Peter
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 12 14:17:22 2006