svn

Checkout a repository to a local directory

$ svn checkout [url] [path/to/directory]

$ svn update

$ svn add [path/to/file]

$ svn commit -m "[message]"

$ svn status

$ svn diff [path/to/file]

$ svn log [path]

$ svn revert [path/to/file]

svn subcommand [options] [args]

svn is the official command-line client for Apache Subversion, a centralized version control system. It manages files and directories over time, tracking modifications and allowing retrieval of previous versions.
The client communicates with a Subversion repository to perform operations like checking out working copies, committing changes, updating to latest revisions, and merging branches. Subversion supports atomic commits, versioned directories, and efficient binary file handling.
Working copies maintain metadata in .svn directories, tracking the base revision and local modifications. The svn client uses this metadata to determine what has changed and what needs synchronization with the repository.

checkout (co)

Check out a working copy from a repository.

Bring changes from the repository into the working copy.

Put files and directories under version control.

Remove files and directories from version control.

Send changes from your working copy to the repository.

Print the status of working copy files and directories.

Display local modifications or differences between revisions.

Display commit log messages.

Undo local modifications to a file or directory.

Apply differences between two sources to a working copy path.

Copy a file or directory in a working copy or repository.

Move or rename a file or directory.

Display information about a local or remote item.

Show author and revision information inline for each line.

Specify a log message for the commit.

Specify a revision number or range (e.g., -r 100, -r 100:200).

Apply change from revision (syntactic sugar for -r rev-1:rev).

Print nothing, or only summary information.

Print extra information.

Limit operation scope: empty, files, immediates, or infinity.

Specify a username for authentication.

Specify a password for authentication.

Do no interactive prompting (useful for scripts).

Unlike Git, Subversion requires network access for most operations since history is stored on the server. The .svn directories in every subdirectory can cause issues when copying working copies. Use svn export instead of copying if you need a clean directory without version control metadata.

Subversion was created by CollabNet in 2000 as a replacement for CVS, addressing its limitations like atomic commits and versioned directories. The project was led by Karl Fogel, Ben Collins-Sussman, and Jim Blandy. Version 1.0 was released in February 2004. Subversion became an Apache Software Foundation project in 2010. While Git has largely supplanted it for open-source development, Subversion remains popular in enterprise environments.

git(1), cvs(1), svnadmin(8), svnserve(8)