While Subversion aimed to take the basic Source Control model already provided by CVS and improve on its design and implementation, SVK aims to open up other Source Control techniques and features offered by other Source Control Systems and models.
Because some of these features are very different to those offered by fully-centralized systems such as CVS and Subversion, there may be a number of techniques or terms that are unfamiliar to you. These will be explained later.
Below is a list of some of the key features provided by SVK
If a repository is being used, all read-only operations are available without a connection to the repository.
It is possible to use SVK without any connection to a repository whatsoever.
Merges between branches are tracked automatically, and therefore do not need manual lists of revision numbers to be specified.
SVK performs very well when compared with other version control systems.###TODO Need more here.
SVK can mirror repositories created by a number of Source Control Systems other than Subversion. ###TODO: List some here
Subversion expresses file differences using a binary differencing algorithm, which works identically on both text (human-readable) and binary (human-unreadable) files. Both types of files are stored equally compressed in the repository, and differences are transmitted in both directions across the network.