- Check out a working copy from a repository:
svn co url/to/repository
- Bring changes from the repository into the working copy:
- Put files and directories under version control, scheduling them for addition to repository. They will be added in next commit:
svn add PATH
- Send changes from your working copy to the repository:
svn ci -m commit_log_message [PATH]
- Display changes from the last 10 revisions, showing modified files for each revision:
svn log -vl 10
- Show detailed help:
svn command [options] [args]
Subversion is a version control system, which allows you to keep old versions of files and directories (usually source code), keep a log of who, when, and why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a single copy of the master sources. This copy is called the source “repository”; it contains all the information to permit extracting previous versions of those files at any time.
For more information about the Subversion project, visit http://subversion.apache.org.
Documentation for Subversion and its tools, including detailed usage explanations of the svn, svnadmin, svnserve and svnlook programs, historical background, philosophical approaches and reasonings, etc., can be found at http://svnbook.red-bean.com/.
Run `svn help' to access the built-in tool documentation.
mgarepo(8), rancid-cvs(1), reposurgeon(1), rsvndump(1), tcsh(1), tkcvs(1), update-smart-drivedb(8).