running svk

Running svk is not hard, however some terms are different from svn's ones. commit is push and update is pull. These may be more intuitive terms than svn's. As I said, svk can reduce revision number of repository. To do this, use -l option for push that means merge everythins into a single commit log.

svk push -l //local/YourProject

Then you can commit your source files after changing few lines without worrying about revision number. I think this is most important thing for refactoring.

Another first step guide of svk. Simple and easy to understand. I do not need boring text but really need sample code or command. When there is something unclear, I will search official document that is more accurate, reliable one than somebody's blog.