svnadmin

svnadmin is the administrative tool for monitoring and repairing your Subversion repository. For detailed information, see the section called “svnadmin”

Since svnadmin works via direct repository access (and thus can only be used on the machine that holds the repository), it refers to the repository with a path, not a URL.

svnadmin Switches

--copies

Follow copy history when examining a path.

--in-repos-template ARG

Specify a template for the repository structure when creating a new repository.

The “in-repository” templates specify the layout of the repository itself (which lives in Berkeley DB files inside the db/ directory) like /trunk, /branches, etc. These templates can be used by an administrator or application to do an initial load of the repository (without invoking hooks). There is no default; the repository is built “empty” unless you tell it otherwise.

--incremental

Dump a revision only as a diff against the previous revision, instead of the usual fulltext.

--on-disk-template ARG

Specify a template to use for the on-disk structure (i.e. conf/, hooks/, etc.) of the repository you want to create.

The “on-disk” templates describe the repository directory itself. Each of the templates have a name, and the “default” on-disk template contains:

  • default/

  • README.txt

  • dav/

  • format

  • hooks/

  • post-commit.tmpl

  • post-revprop-change.tmpl

  • pre-commit.tmpl

  • pre-revprop-change.tmpl

  • start-commit.tmpl

  • locks/

  • db.lock

The typical usage for the on-disk structures is to predefine the hook scripts that will be created. For example, you could prepopulate the post-commit script with a commit mailer and backup script. Then, each time the administrator creates a new repository, she can refer to this new template which automagically includes all of the hooks.

--revision (-r) ARG

Specify a particular revision to operate on.

svnadmin Subcommands