From: Adrian Howard <adrianh@...>
Date: 2007-03-22T00:52:45+09:00
Subject: Re: Why SVN?


On 21 Mar 2007, at 15:30, Greg Hurrell wrote:

> On 21 mar, 10:49, Adrian Howard <adri...@quietstars.com> wrote:
>>
>> You might want to consider using SVK as your client (if you're happy
>> using the command line). It's a distributed system built on top of
>> subversion - so you can mirror subversion repos locally and push/pull
>> changes between your local copy and the main one.
>>
>> I've been using it for about a year as my primary way of talking to
>> subversion and have been very happy with it.
>
> Adrian, I'd love to hear more about your workflow. Could you give an
> example of how you use this set-up for things like branching and
> merging?

Assuming $R is my "master" subversion repository I do something like  
this

1) At the start of a project set up a mirror...

     svk mirror $R/project/foo/trunk //foo/trunk

2) ... and a local branch

     svk cp //foo/trunk //foo/local -m 'a local branch for local folk'

3) Check out a working copy into the foo directory

     svk co //foo/local foo

4) Pull changes down from the central server

     svk pull foo

I can then merrily work away in my local foo working copy committing  
to my local branch on my local machine. When I want to push my  
changes back to the central server I do

     svk push --verbatim foo

(The --verbatim bit reproduces the commits you made to the local repo  
on the remote one, rather than merging them into one big commit.  
Makes it easier to track changes)

That's basically it.

Cheers,

Adrian