Table of Contents
This chapter is intended to be a complete reference to using Subversion. This includes the command line client (svn) and all its subcommands, as well as the repository administration programs (svnadmin and svnlook) and their respective subcommands.
To use the command line client, you type svn, the subcommand you wish to use [42], and any switches or targets that you wish to operate on—there is no specific order that the subcommand and the switches must appear in. For example, all of the following are valid ways to use svn status:
$ svn -v status $ svn status -v $ svn status -v myfile
You can find many more examples of how to use most client commands in Chapter 3, Guided Tour and commands for managing properties in the section called “Properties”.
While Subversion has different switches for its subcommands, all switches are global—that is, each switch is guaranteed to mean the same thing regardless of the subcommand you use it with. For example, --verbose (-v) always means “verbose output”, regardless of the subcommand you use it with.
Enables auto-props, overriding the enable-auto-props directive in the config file.
Instructs Subversion to read configuration information from the specified directory instead of the default location (.subversion in the user's home directory).
Specifies an external program to use to show differences between files. When svn diff is invoked, it uses Subversion's internal diff engine, which provides unified diffs by default. If you want to use an external diff program, use --diff-cmd. You can pass switches to the diff program with the --extensions switch (more on that later in this section).
Specifies an external program to use to merge files.
Goes through all the motions of running a command, but makes no actual changes—either on disk or in the repository.
Specifies an external program to use to edit a log message or a property value.
Tells Subversion that your commit message is encoded in the charset provided. The default is your operating system's native locale, and you should specify the encoding if your commit message is in any other encoding.
Specifies an argument or arguments that Subversion should pass to an external diff command when providing differences between files. If you wish to pass multiple arguments, you must enclose all of them in quotes (for example, svn diff --diff-cmd /usr/bin/diff -x "-b -E"). This switch can only be used if you also pass the --diff-cmd switch.
Uses the contents of the file passed as an argument to this switch for the specified subcommand.
Forces a particular command or operation to run. There are some operations that Subversion will prevent you from doing in normal usage, but you can pass the force switch to tell Subversion “I know what I'm doing as well as the possible repercussions of doing it, so let me at 'em”. This switch is the programmatic equivalent of doing your own electrical work with the power on—if you don't know what you're doing, you're likely to get a nasty shock.
Forces a suspicious parameter passed to the --message (-m) or --file (-F) options to be accepted as valid. By default, Subversion will produce an error if parameters to these options look like they might instead be targets of the subcommand. For example, if you pass a versioned file's path to the --file (-F) option, Subversion will assume you've made a mistake, that the path was instead intended as the target of the operation, and that you simply failed to provide some other—unversioned—file as the source of your log message. To assert your intent and override these types of errors, pass the --force-log option to commands that accept log messages.
If used with one or more subcommands, shows the built-in help text for each subcommand. If used alone, it displays the general client help text.
Tells Subversion to ignore ancestry when calculating differences (rely on path contents alone).
Prints output in a format suitable for concatenation.
Indicates that you will specify a commit message on the command line, following this switch. For example:
$ svn commit -m "They don't make Sunday."
Uses ARG as the newer target.
Prevents caching of authentication information (e.g. username and password) in the Subversion administrative directories.
Disables auto-props, overriding the enable-auto-props directive in the config file.
Prevents Subversion from printing differences for deleted files. The default behavior when you remove a file is for svn diff to print the same differences that you would see if you had left the file but removed all the content.
Shows files in the status listing that would normally be omitted since they match a pattern in the global-ignores configuration option or the svn:ignore property. See the section called “Config” and the section called “svn:ignore” for more information.
In the case of an authentication failure, or insufficient credentials, prevents prompting for credentials (e.g. username or password). This is useful if you're running Subversion inside of an automated script and it's more appropriate to have Subversion fail than to prompt for more information.
Stops a subcommand from recursing into subdirectories. Most subcommands recurse by default, but some subcommands—usually those that have the potential to remove or undo your local modifications—do not.
Pay attention to ancestry when calculating differences.
Uses ARG as the older target.
Indicates that you are providing your password for authentication on the command line—otherwise, if it is needed, Subversion will prompt you for it.
Requests that the client print only essential information while performing an operation.
Makes a subcommand recurse into subdirectories. Most subcommands recurse by default.
Used with the svn switch subcommand, changes the location of the repository that your working copy references. This is useful if the location of your repository changes and you have an existing working copy that you'd like to continue to use. See svn switch for an example.
Indicates that you're going to supply a revision (or range of revisions) for a particular operation. You can provide revision numbers, revision keywords or dates (in curly braces), as arguments to the revision switch. If you wish to provide a range of revisions, you can provide two revisions separated by a colon. For example:
$ svn log -r 1729 $ svn log -r 1729:HEAD $ svn log -r 1729:1744 $ svn log -r {2001-12-04}:{2002-02-17} $ svn log -r 1729:{2002-02-17}
See the section called “Revision Keywords” for more information.
Operates on a revision property instead of a Subversion property specific to a file or directory. This switch requires that you also pass a revision with the --revision (-r) switch. See the section called “Unversioned Properties” for more details on unversioned properties.
Causes the client to display information about which files in your working copy are out-of-date. This doesn't actually update any of your files—it just shows you which files will be updated if you run svn update.
Causes a Subversion subcommand which is traversing the history of a versioned resource to stop harvesting that historical information when a copy—that is, a location in history where that resource was copied from another location in the repository—is encountered.
Causes Subversion to use strict semantics, a notion which is rather vague unless talking about specific subcommands.
Tells Subversion to get the list of files that you wish to operate on from the filename you provide instead of listing all the files on the command line.
Indicates that you are providing your username for authentication on the command line—otherwise, if it is needed, Subversion will prompt you for it.
Requests that the client print out as much information as it can while running any subcommand. This may result in Subversion printing out additional fields, detailed information about every file, or additional information regarding its actions.
Prints the client version info. This information not only includes the version number of the client, but also a listing of all repository access modules that the client can use to access a Subversion repository.
Prints output in XML format.
[42] Yes, yes, you don't need a subcommand to use the --version switch, but we'll get to that in just a minute.