Version Control with Subversion - Login

Chapter 9. Subversion CompleteReferenceThis chapter is intended to be a complete reference to using Subversion. This includes thecommand-line client (svn) and all its subcommands, as well as the repository administrationprograms (svnadmin and svnlook) and their respective subcommands.The Subversion Command-Line Client: svnTo use the command-line client, type svn, the subcommand you wish to use, 1 and any optionsor targets that you wish to operate on—the subcommand and the options need notappear in a specific order. For example, all of the following are valid ways to use svnstatus:$ svn -v status$ svn status -v$ svn status -v myfileYou can find many more examples of how to use most client commands in Chapter 2, BasicUsage and commands for managing properties in the section called “Properties”.svn OptionsWhile Subversion has different options for its subcommands, all options exist in a singlenamespace—that is, each option is guaranteed to mean the same thing regardless of thesubcommand you use it with. For example, --verbose (-v) always means “verbose output,”regardless of the subcommand you use it with.The svn command-line client usually exits quickly with an error if you pass it an optionwhich does not apply to the specified subcommand. But as of Subversion 1.5, several ofthe options which apply to all—or nearly all—of the subcommands have been deemed acceptableby all subcommands, even if they have no effect on some of them. They appeargrouped together in the command-line client's usage messages as global options. This wasdone to assist folks who write scripts which wrap the command-line client. These global optionsare as follows:--config-dir DIRInstructs Subversion to read configuration information from the specified directory insteadof the default location (.subversion in the user's home directory).--no-auth-cachePrevents caching of authentication information (e.g., username and password) in theSubversion runtime configuration directories.--non-interactiveDisables all interactive prompting. Some examples of interactive prompting include requestsfor authentication credentials and conflict resolution decisions. This is useful ifyou're running Subversion inside an automated script and it's more appropriate to haveSubversion fail than to prompt for more information.--password PASSWDSpecifies the password to use when authenticating against a Subversion server. If notprovided, or if incorrect, Subversion will prompt you for this information as needed.1 Well, you don't need a subcommand to use the --version option, but we'll get to that in just a minute.222