Manual Reference Pages - SVK::HELP::INTRO (3)
SVK::Help::Intro - Introduction to svk
svk is an open source distributed version control system which is
designed to interoperate with Subversion. Like other version control
systems, it keeps track of each change you make to a project and allows
you to maintain multiple parallel tracks of development. svk also has
a number of powerful features which are rarely found in other version
svk has been designed from the ground up to support development
models that are simple and intuitive for software developers. It has
advanced smart branching and merging semantics that make it easy to
maintain multiple parallel lines of development and painless to merge
changes across branches. svks built in patch manager makes it easy
for non-committers to share changes among themselves and with project
svk provides powerful support for distributed development. Every svk
client is capable of fully mirroring remote Subversion repositories so
that you have full access to a projects history at any time, even when
they are off the network or on the wrong side of a firewall. You can
branch a remote project at any point in that projects history, whether
or not you have write access to that projects repository. Later, you
can integrate changes from the projects master server (usually with a
single command) or push your branch up to another Subversion repository.
svk has a rich command line interface that can be somewhat daunting
at first. the following few commands are all youll need for day to
To see a full list of svks commands, type svk help commands.
For help with a specific command, just type svk help command.
First, youll need to mirror a remote repository. This sets up a local
copy of that repository for you to branch from, merge to and otherwise
poke at. The local path is sometimes called a depot path.
svk mirror svn://svn.example.com/project_x //mirror/project_x
When youve set up a new mirror or want to get some work done without
a network connection, sync your local repository with upstream
svk sync //mirror/project_x
When you want to get some work done, you can checkout a working copy
to make changes.
svk co //mirror/project_x
If you want to work offline, you can create a local branch
svk branch --offline
svk add, svk delete and svk move
As you work on the files in your working copy, feel free to add
new files, delete existing files and move files around.
svk add Changelog
svk move badly_named_file.c well_named_file.c
svk delete .README.swp
When youre done, just commit your changes to your local repository,
whether or not you have network. If you commit to a mirrored path,
rather than a local branch, youll need to be able to access the paths
upstream subversion server, but the commit will be sent to the server
Life doesnt stop when you make a local branch. From time to time,
pull down changes from the upstream repository.
When youre ready to share your changes with the world, push them to
the upstream repository.
The svk wiki (<http://svk.bestpractical.com>) is a great place to find the
latest svk tips, tricks and updates. If you run into trouble using svk,
the wikis the right place to start looking for help.
|perl v5.20.3 ||SVK::HELP::INTRO (3) ||2008-09-13 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.