[svnbook] r4425 committed - * en/book/ref-svnadmin.xml...
svnbook at googlecode.com
svnbook at googlecode.com
Tue Feb 12 10:54:57 CST 2013
Revision: 4425
Author: cmpilato at gmail.com
Date: Tue Feb 12 08:54:42 2013
Log: * en/book/ref-svnadmin.xml
Fix indentation/whitespace/comments.
http://code.google.com/p/svnbook/source/detail?r=4425
Modified:
/trunk/en/book/ref-svnadmin.xml
=======================================
--- /trunk/en/book/ref-svnadmin.xml Thu Feb 7 12:43:50 2013
+++ /trunk/en/book/ref-svnadmin.xml Tue Feb 12 08:54:42 2013
@@ -3,9 +3,6 @@
<reference id="svn.ref.svnadmin">
<title>svnadmin Reference—Subversion Repository
Administration</title>
- <!-- =================================================================
-->
- <!-- =================================================================
-->
- <!-- =================================================================
-->
<partintro>
<para><command>svnadmin</command> is the administrative tool for
monitoring and repairing your Subversion repository. For
@@ -16,337 +13,335 @@
(and thus can only be used on the machine that holds the
repository), it refers to the repository with a path, not a
URL.</para>
- <para>Options in <command>svnadmin</command> are global, just
- as they are in <command>svn</command>:</para>
+ <para>Options in <command>svnadmin</command> are global, just
+ as they are in <command>svn</command>:</para>
- <variablelist id="svn.ref.svnadmin.sw">
- <title>svnadmin Options</title>
-
- <varlistentry id="svn.ref.svnadmin.sw.bdb_log_keep">
- <term><option>--bdb-log-keep</option></term>
- <listitem>
- <para>(Berkeley DB-specific.) Disable automatic log removal
- of database logfiles. Having these logfiles around
- can be convenient if you need to restore from a
- catastrophic repository failure.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="svn.ref.svnadmin.sw.bdb_txn_nosync">
- <term><option>--bdb-txn-nosync</option></term>
- <listitem>
+ <variablelist id="svn.ref.svnadmin.sw">
+ <title>svnadmin Options</title>
+
+ <varlistentry id="svn.ref.svnadmin.sw.bdb_log_keep">
+ <term><option>--bdb-log-keep</option></term>
+ <listitem>
+ <para>(Berkeley DB-specific.) Disable automatic log removal
+ of database logfiles. Having these logfiles around
+ can be convenient if you need to restore from a
+ catastrophic repository failure.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry id="svn.ref.svnadmin.sw.bdb_txn_nosync">
+ <term><option>--bdb-txn-nosync</option></term>
+ <listitem>
- <para>(Berkeley DB-specific.) Disables fsync when
- committing database transactions. Used with the
- <command>svnadmin create</command> command to create a
- Berkeley DB-backed repository with
- <literal>DB_TXN_NOSYNC</literal> enabled (which improves
- speed but has some risks associated with it).</para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="svn.ref.svnadmin.sw.bypass_hooks">
- <term><option>--bypass-hooks</option></term>
- <listitem>
- <para>Bypass the repository hook system.</para>
- </listitem>
- </varlistentry>
+ <para>(Berkeley DB-specific.) Disables fsync when
+ committing database transactions. Used with the
+ <command>svnadmin create</command> command to create a
+ Berkeley DB-backed repository with
+ <literal>DB_TXN_NOSYNC</literal> enabled (which improves
+ speed but has some risks associated with it).</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry id="svn.ref.svnadmin.sw.bypass_hooks">
+ <term><option>--bypass-hooks</option></term>
+ <listitem>
+ <para>Bypass the repository hook system.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.bypass_prop_validation">
- <term><option>--bypass-prop-validation</option></term>
- <listitem>
- <para>When loading a dump file, disable the logic which
- validates property values.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.bypass_prop_validation">
+ <term><option>--bypass-prop-validation</option></term>
+ <listitem>
+ <para>When loading a dump file, disable the logic which
+ validates property values.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.clean_logs">
- <term><option>--clean-logs</option></term>
- <listitem>
- <para>Remove unused Berkeley DB logs.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.clean_logs">
+ <term><option>--clean-logs</option></term>
+ <listitem>
+ <para>Remove unused Berkeley DB logs.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.config_dir">
- <!-- Only 'svnadmin create' accepts it, and the underlying
- logic doesn't even use it. Weird. -->
- <term><option>--config-dir</option>
<replaceable>DIR</replaceable></term>
- <listitem>
- <para>Instructs Subversion to read configuration
- information from the specified directory instead of the
- default location (<filename>.subversion</filename> in
- the user's home directory).</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.config_dir">
+ <!-- Only 'svnadmin create' accepts it, and the underlying
+ logic doesn't even use it. Weird. -->
+ <term><option>--config-dir</option>
<replaceable>DIR</replaceable></term>
+ <listitem>
+ <para>Instructs Subversion to read configuration
+ information from the specified directory instead of the
+ default location (<filename>.subversion</filename> in
+ the user's home directory).</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.deltas">
- <term><option>--deltas</option></term>
- <listitem>
- <para>When creating a repository dump file, specify
- changes in versioned properties and file contents as
- deltas against their previous state.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.deltas">
+ <term><option>--deltas</option></term>
+ <listitem>
+ <para>When creating a repository dump file, specify
+ changes in versioned properties and file contents as
+ deltas against their previous state.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.fs_type">
- <term><option>--fs-type</option>
<replaceable>ARG</replaceable></term>
- <listitem>
- <para>When creating a repository,
- use <replaceable>ARG</replaceable> as the requested
- filesyste type. <replaceable>ARG</replaceable> may be
- either <literal>bdb</literal>
- or <literal>fsfs</literal>.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.fs_type">
+ <term><option>--fs-type</option>
<replaceable>ARG</replaceable></term>
+ <listitem>
+ <para>When creating a repository,
+ use <replaceable>ARG</replaceable> as the requested
+ filesyste type. <replaceable>ARG</replaceable> may be
+ either <literal>bdb</literal>
+ or <literal>fsfs</literal>.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.force_uuid">
- <term><option>--force-uuid</option></term>
- <listitem>
- <para>By default, when loading data into a repository that
- already contains revisions, <command>svnadmin</command>
- will ignore the UUID from the dump stream. This option
- will cause the repository's UUID to be set to the UUID
- from the stream.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.force_uuid">
+ <term><option>--force-uuid</option></term>
+ <listitem>
+ <para>By default, when loading data into a repository that
+ already contains revisions, <command>svnadmin</command>
+ will ignore the UUID from the dump stream. This option
+ will cause the repository's UUID to be set to the UUID
+ from the stream.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.ignore_uuid">
- <term><option>--ignore-uuid</option></term>
- <listitem>
- <para>By default, when loading data into an empty repository,
- <command>svnadmin</command> will set the repository's UUID
- to the UUID from the dump stream. This option will cause
- the UUID from the stream to be ignored.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.ignore_uuid">
+ <term><option>--ignore-uuid</option></term>
+ <listitem>
+ <para>By default, when loading data into an empty repository,
+ <command>svnadmin</command> will set the repository's UUID
+ to the UUID from the dump stream. This option will cause
+ the UUID from the stream to be ignored.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.incremental">
- <term><option>--incremental</option></term>
- <listitem>
- <para>Dump a revision only as a diff against the
- previous revision, instead of the usual
- fulltext.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.incremental">
+ <term><option>--incremental</option></term>
+ <listitem>
+ <para>Dump a revision only as a diff against the
+ previous revision, instead of the usual
+ fulltext.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.memory_cache_size">
- <term><option>--memory-cache-size</option> (<option>-M</option>)
<replaceable>ARG</replaceable></term>
- <listitem>
- <para>Configures the size (in Megabytes) of the extra
- in-memory cache used to minimize redundant operations.
- The default value is <literal>16</literal>. (This cache
- is used for FSFS-backed repositories only.)</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.memory_cache_size">
+ <term><option>--memory-cache-size</option> (<option>-M</option>)
<replaceable>ARG</replaceable></term>
+ <listitem>
+ <para>Configures the size (in Megabytes) of the extra
+ in-memory cache used to minimize redundant operations.
+ The default value is <literal>16</literal>. (This cache
+ is used for FSFS-backed repositories only.)</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.parent_dir">
- <term><option>--parent-dir</option>
<replaceable>DIR</replaceable></term>
- <listitem>
- <para>When loading a dump file, root paths at
- <replaceable>DIR</replaceable> instead of
- <filename>/</filename>.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.parent_dir">
+ <term><option>--parent-dir</option>
<replaceable>DIR</replaceable></term>
+ <listitem>
+ <para>When loading a dump file, root paths at
+ <replaceable>DIR</replaceable> instead of
+ <filename>/</filename>.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.pre_1.4_compatible">
- <term><option>--pre-1.4-compatible</option></term>
- <listitem>
- <para>When creating a new repository, use a format that is
- compatible with versions of Subversion earlier than
- Subversion 1.4.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.pre_1.4_compatible">
+ <term><option>--pre-1.4-compatible</option></term>
+ <listitem>
+ <para>When creating a new repository, use a format that is
+ compatible with versions of Subversion earlier than
+ Subversion 1.4.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.pre_1.5_compatible">
- <term><option>--pre-1.5-compatible</option></term>
- <listitem>
- <para>When creating a new repository, use a format that is
- compatible with versions of Subversion earlier than
- Subversion 1.5.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.pre_1.5_compatible">
+ <term><option>--pre-1.5-compatible</option></term>
+ <listitem>
+ <para>When creating a new repository, use a format that is
+ compatible with versions of Subversion earlier than
+ Subversion 1.5.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.pre_1.6_compatible">
- <term><option>--pre-1.6-compatible</option></term>
- <listitem>
- <para>When creating a new repository, use a format that is
- compatible with versions of Subversion earlier than
- Subversion 1.6.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.pre_1.6_compatible">
+ <term><option>--pre-1.6-compatible</option></term>
+ <listitem>
+ <para>When creating a new repository, use a format that is
+ compatible with versions of Subversion earlier than
+ Subversion 1.6.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.revision">
- <term><option>--revision</option> (<option>-r</option>)
<replaceable>ARG</replaceable></term>
- <listitem>
- <para>Specify a particular revision to operate
- on.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.revision">
+ <term><option>--revision</option> (<option>-r</option>)
<replaceable>ARG</replaceable></term>
+ <listitem>
+ <para>Specify a particular revision to operate
+ on.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.quiet">
- <term><option>--quiet</option> (<option>-q</option>)</term>
- <listitem>
- <para>Do not show normal progress—show only
- errors.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.quiet">
+ <term><option>--quiet</option> (<option>-q</option>)</term>
+ <listitem>
+ <para>Do not show normal progress—show only
+ errors.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.use_post_commit_hook">
- <term><option>--use-post-commit-hook</option></term>
- <listitem>
- <para>When loading a dump file, runs the repository's
- <literal>post-commit</literal> hook after finalizing each
newly loaded
- revision.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.use_post_commit_hook">
+ <term><option>--use-post-commit-hook</option></term>
+ <listitem>
+ <para>When loading a dump file, runs the repository's
+ <literal>post-commit</literal> hook after finalizing each
newly loaded
+ revision.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry
id="svn.ref.svnadmin.sw.use_post_revprop_change_hook">
- <term><option>--use-post-revprop-change-hook</option></term>
- <listitem>
- <para>When changing a revision property, runs the
- repository's <literal>post-revprop-change</literal> hook
after changing the
- revision property.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.use_post_revprop_change_hook">
+ <term><option>--use-post-revprop-change-hook</option></term>
+ <listitem>
+ <para>When changing a revision property, runs the
+ repository's <literal>post-revprop-change</literal> hook after
changing the
+ revision property.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.use_pre_commit_hook">
- <term><option>--use-pre-commit-hook</option></term>
- <listitem>
- <para>When loading a dump file, runs the repository's
- <literal>pre-commit</literal> hook before finalizing each
newly loaded
- revision. If the hook fails, aborts the commit and
- terminates the load process.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.use_pre_commit_hook">
+ <term><option>--use-pre-commit-hook</option></term>
+ <listitem>
+ <para>When loading a dump file, runs the repository's
+ <literal>pre-commit</literal> hook before finalizing each
newly loaded
+ revision. If the hook fails, aborts the commit and
+ terminates the load process.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.use_pre_revprop_change_hook">
- <term><option>--use-pre-revprop-change-hook</option></term>
- <listitem>
- <para>When changing a revision property, runs the
- repository's <literal>pre-revprop-change</literal> hook
before changing the
- revision property. If the hook fails, aborts the
- modification and terminates.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.use_pre_revprop_change_hook">
+ <term><option>--use-pre-revprop-change-hook</option></term>
+ <listitem>
+ <para>When changing a revision property, runs the
+ repository's <literal>pre-revprop-change</literal> hook before
changing the
+ revision property. If the hook fails, aborts the
+ modification and terminates.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry id="svn.ref.svnadmin.sw.wait">
- <term><option>--wait</option></term>
- <listitem>
- <para>For operations which require exclusive repository
- access, wait until the requisite repository lock has
- been obtained instead of immediately erroring out when
- it cannot be.</para>
- </listitem>
- </varlistentry>
+ <varlistentry id="svn.ref.svnadmin.sw.wait">
+ <term><option>--wait</option></term>
+ <listitem>
+ <para>For operations which require exclusive repository
+ access, wait until the requisite repository lock has
+ been obtained instead of immediately erroring out when
+ it cannot be.</para>
+ </listitem>
+ </varlistentry>
- </variablelist>
+ </variablelist>
</partintro>
- <!-- ===============================================================
-->
-
- <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
- <refentry id="svn.ref.svnadmin.c.crashtest">
+ <!-- =============================================================== -->
+ <refentry id="svn.ref.svnadmin.c.crashtest">
- <indexterm>
- <primary>svnadmin</primary>
- <secondary>subcommands</secondary>
- <tertiary>crashtest</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>crashtest</tertiary>
+ </indexterm>
- <refnamediv>
- <refname>svnadmin crashtest</refname>
- <refpurpose>Simulate a process that crashes.</refpurpose>
- </refnamediv>
- <refsect1>
- <title>Synopsis</title>
- <para><literal>svnadmin crashtest REPOS_PATH</literal></para>
- </refsect1>
- <refsect1>
- <title>Description</title>
+ <refnamediv>
+ <refname>svnadmin crashtest</refname>
+ <refpurpose>Simulate a process that crashes.</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svnadmin crashtest REPOS_PATH</literal></para>
+ </refsect1>
+ <refsect1>
+ <title>Description</title>
- <para>Open the repository at
<replaceable>REPOS_PATH</replaceable>, then abort, thus
- simulating a process that crashes while holding an open
- repository handle. This is used for testing automatic
- repository recovery (a new feature in Berkeley DB 4.4).
- It's unlikely that you'll need to run this
- command.</para>
+ <para>Open the repository at
<replaceable>REPOS_PATH</replaceable>, then abort, thus
+ simulating a process that crashes while holding an open
+ repository handle. This is used for testing automatic
+ repository recovery (a new feature in Berkeley DB 4.4).
+ It's unlikely that you'll need to run this
+ command.</para>
- </refsect1>
+ </refsect1>
- <refsect1>
- <title>Options</title>
+ <refsect1>
+ <title>Options</title>
- <para>None</para>
+ <para>None</para>
- </refsect1>
+ </refsect1>
- <refsect1>
- <title>Examples</title>
+ <refsect1>
+ <title>Examples</title>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
$ svnadmin crashtest /var/svn/repos
Aborted
</screen>
- </informalexample>
+ </informalexample>
- <para>Exciting, isn't it?</para>
-
- </refsect1>
- </refentry>
+ <para>Exciting, isn't it?</para>
+
+ </refsect1>
+ </refentry>
- <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
- <refentry id="svn.ref.svnadmin.c.create">
+ <!-- =============================================================== -->
+ <refentry id="svn.ref.svnadmin.c.create">
- <indexterm>
- <primary>svnadmin</primary>
- <secondary>subcommands</secondary>
- <tertiary>create</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>create</tertiary>
+ </indexterm>
- <refnamediv>
- <refname>svnadmin create</refname>
- <refpurpose>Create a new, empty repository.</refpurpose>
- </refnamediv>
- <refsect1>
- <title>Synopsis</title>
- <para><literal>svnadmin create REPOS_PATH</literal></para>
- </refsect1>
- <refsect1>
- <title>Description</title>
+ <refnamediv>
+ <refname>svnadmin create</refname>
+ <refpurpose>Create a new, empty repository.</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svnadmin create REPOS_PATH</literal></para>
+ </refsect1>
+ <refsect1>
+ <title>Description</title>
- <para>Create a new, empty repository at the path provided.
- If the provided directory does not exist, it will be
- created for
- you.<footnote><para>Remember, <command>svnadmin</command>
- works only with local <emphasis>paths</emphasis>, not
- <emphasis>URLs</emphasis>.</para></footnote> As of
- Subversion 1.2, <command>svnadmin</command> creates new
- repositories with the
- <literal>FSFS</literal> filesystem backend by
- default.</para>
+ <para>Create a new, empty repository at the path provided.
+ If the provided directory does not exist, it will be
+ created for
+ you.<footnote><para>Remember, <command>svnadmin</command>
+ works only with local <emphasis>paths</emphasis>, not
+ <emphasis>URLs</emphasis>.</para></footnote> As of
+ Subversion 1.2, <command>svnadmin</command> creates new
+ repositories with the
+ <literal>FSFS</literal> filesystem backend by
+ default.</para>
- <para>While <command>svnadmin create</command> will create
- the base directory for a new repository, it will not
- create intermediate directories. For example, if you
- have an empty directory named
- <filename>/var/svn</filename>, creating
- <filename>/var/svn/repos</filename> will work, while
- attempting to create
- <filename>/var/svn/subdirectory/repos</filename> will
- fail with an error. Also, keep in mind that, depending
- on where on your system you are creating your
- repository, you might need to run <command>svnadmin
- create</command> as a user with elevated privileges
- (such as the <literal>root</literal> user).</para>
+ <para>While <command>svnadmin create</command> will create
+ the base directory for a new repository, it will not
+ create intermediate directories. For example, if you
+ have an empty directory named
+ <filename>/var/svn</filename>, creating
+ <filename>/var/svn/repos</filename> will work, while
+ attempting to create
+ <filename>/var/svn/subdirectory/repos</filename> will
+ fail with an error. Also, keep in mind that, depending
+ on where on your system you are creating your
+ repository, you might need to run <command>svnadmin
+ create</command> as a user with elevated privileges
+ (such as the <literal>root</literal> user).</para>
- </refsect1>
+ </refsect1>
- <refsect1>
- <title>Options</title>
+ <refsect1>
+ <title>Options</title>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
<xref linkend="svn.ref.svnadmin.sw.bdb_log_keep" />
<xref linkend="svn.ref.svnadmin.sw.bdb_txn_nosync" />
<xref linkend="svn.ref.svnadmin.sw.config_dir" />
@@ -355,349 +350,349 @@
<xref linkend="svn.ref.svnadmin.sw.pre_1.5_compatible" />
<xref linkend="svn.ref.svnadmin.sw.pre_1.6_compatible" />
</screen>
- </informalexample>
- </refsect1>
+ </informalexample>
+ </refsect1>
- <refsect1>
- <title>Examples</title>
+ <refsect1>
+ <title>Examples</title>
- <para>Creating a new repository is this easy:</para>
+ <para>Creating a new repository is this easy:</para>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
$ cd /var/svn
$ svnadmin create repos
$
</screen>
- </informalexample>
-
- <para>In Subversion 1.0, a Berkeley DB repository is always
- created. In Subversion 1.1, a Berkeley DB repository is
- the default repository type, but an FSFS repository can be
- created using the <option>--fs-type</option>
- option:</para>
+ </informalexample>
+
+ <para>In Subversion 1.0, a Berkeley DB repository is always
+ created. In Subversion 1.1, a Berkeley DB repository is
+ the default repository type, but an FSFS repository can be
+ created using the <option>--fs-type</option>
+ option:</para>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
$ cd /var/svn
$ svnadmin create repos --fs-type fsfs
$
</screen>
- </informalexample>
+ </informalexample>
- </refsect1>
- </refentry>
+ </refsect1>
+ </refentry>
- <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
- <refentry id="svn.ref.svnadmin.c.deltify">
+ <!-- =============================================================== -->
+ <refentry id="svn.ref.svnadmin.c.deltify">
- <indexterm>
- <primary>svnadmin</primary>
- <secondary>subcommands</secondary>
- <tertiary>deltify</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>deltify</tertiary>
+ </indexterm>
- <refnamediv>
- <refname>svnadmin deltify</refname>
- <refpurpose>Deltify changed paths in a revision
range.</refpurpose>
- </refnamediv>
- <refsect1>
- <title>Synopsis</title>
- <para><literal>svnadmin deltify [-r LOWER[:UPPER]]
REPOS_PATH</literal></para>
- </refsect1>
- <refsect1>
- <title>Description</title>
+ <refnamediv>
+ <refname>svnadmin deltify</refname>
+ <refpurpose>Deltify changed paths in a revision range.</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svnadmin deltify [-r LOWER[:UPPER]]
REPOS_PATH</literal></para>
+ </refsect1>
+ <refsect1>
+ <title>Description</title>
- <para><command>svnadmin deltify</command> exists in
- current versions of Subversion only for historical reasons.
- This command is deprecated and no longer needed.</para>
+ <para><command>svnadmin deltify</command> exists in
+ current versions of Subversion only for historical reasons.
+ This command is deprecated and no longer needed.</para>
- <para>It dates from a time when Subversion offered
- administrators greater control over compression strategies
- in the repository. This turned out to be a lot of
- complexity for <emphasis>very</emphasis> little gain, and
- this <quote>feature</quote> was deprecated.</para>
+ <para>It dates from a time when Subversion offered
+ administrators greater control over compression strategies
+ in the repository. This turned out to be a lot of
+ complexity for <emphasis>very</emphasis> little gain, and
+ this <quote>feature</quote> was deprecated.</para>
- </refsect1>
- <refsect1>
- <title>Options</title>
+ </refsect1>
+ <refsect1>
+ <title>Options</title>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
<xref linkend="svn.ref.svnadmin.sw.memory_cache_size" />
<xref linkend="svn.ref.svnadmin.sw.quiet" />
<xref linkend="svn.ref.svnadmin.sw.revision" />
</screen>
- </informalexample>
- </refsect1>
- </refentry>
+ </informalexample>
+ </refsect1>
+ </refentry>
- <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
- <refentry id="svn.ref.svnadmin.c.dump">
+ <!-- =============================================================== -->
+ <refentry id="svn.ref.svnadmin.c.dump">
- <indexterm>
- <primary>svnadmin</primary>
- <secondary>subcommands</secondary>
- <tertiary>dump</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>dump</tertiary>
+ </indexterm>
- <refnamediv>
- <refname>svnadmin dump</refname>
- <refpurpose>Dump the contents of the filesystem to
<filename>stdout</filename>.</refpurpose>
- </refnamediv>
- <refsect1>
- <title>Synopsis</title>
- <para><literal>svnadmin dump REPOS_PATH [-r LOWER[:UPPER]]
[--incremental] [--deltas]</literal></para>
- </refsect1>
- <refsect1>
- <title>Description</title>
+ <refnamediv>
+ <refname>svnadmin dump</refname>
+ <refpurpose>Dump the contents of the filesystem to
<filename>stdout</filename>.</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svnadmin dump REPOS_PATH [-r LOWER[:UPPER]]
[--incremental] [--deltas]</literal></para>
+ </refsect1>
+ <refsect1>
+ <title>Description</title>
- <para>Dump the contents of the filesystem to
<filename>stdout</filename> in a
- <quote>dump file</quote> portable format, sending feedback
- to <filename>stderr</filename>. Dump revisions
- <replaceable>LOWER</replaceable> rev through
- <replaceable>UPPER</replaceable> rev. If no revisions are
- given, dump all revision trees. If only
- <replaceable>LOWER</replaceable> is given, dump that one
- revision tree. See <xref
linkend="svn.reposadmin.maint.migrate"/>
- for a practical use.</para>
+ <para>Dump the contents of the filesystem to
<filename>stdout</filename> in a
+ <quote>dump file</quote> portable format, sending feedback
+ to <filename>stderr</filename>. Dump revisions
+ <replaceable>LOWER</replaceable> rev through
+ <replaceable>UPPER</replaceable> rev. If no revisions are
+ given, dump all revision trees. If only
+ <replaceable>LOWER</replaceable> is given, dump that one
+ revision tree. See <xref linkend="svn.reposadmin.maint.migrate"/>
+ for a practical use.</para>
- <para>By default, the Subversion dump stream contains a
- single revision (the first revision in the requested
- revision range) in which every file and directory in the
- repository in that revision is presented as though that whole
- tree was added at once, followed by other revisions (the
- remainder of the revisions in the requested range), which
- contain only the files and directories that were modified
- in those revisions. For a modified file, the complete
- full-text representation of its contents, as well as all of
- its properties, are presented in the dump file; for a
- directory, all of its properties are presented.</para>
+ <para>By default, the Subversion dump stream contains a
+ single revision (the first revision in the requested
+ revision range) in which every file and directory in the
+ repository in that revision is presented as though that whole
+ tree was added at once, followed by other revisions (the
+ remainder of the revisions in the requested range), which
+ contain only the files and directories that were modified
+ in those revisions. For a modified file, the complete
+ full-text representation of its contents, as well as all of
+ its properties, are presented in the dump file; for a
+ directory, all of its properties are presented.</para>
- <para>Two useful options modify the dump file
- generator's behavior. The first is the
- <option>--incremental</option> option, which simply causes
- that first revision in the dump stream to contain only
- the files and directories modified in that revision,
- instead of being presented as the addition of a new tree,
- and in exactly the same way that every other revision in
- the dump file is presented. This is useful for generating
- a relatively small dump file to be loaded into another
- repository that already has the files and directories
- that exist in the original repository.</para>
+ <para>Two useful options modify the dump file
+ generator's behavior. The first is the
+ <option>--incremental</option> option, which simply causes
+ that first revision in the dump stream to contain only
+ the files and directories modified in that revision,
+ instead of being presented as the addition of a new tree,
+ and in exactly the same way that every other revision in
+ the dump file is presented. This is useful for generating
+ a relatively small dump file to be loaded into another
+ repository that already has the files and directories
+ that exist in the original repository.</para>
- <para>The second useful option is <option>--deltas</option>.
- This option causes <command>svnadmin dump</command> to,
- instead of emitting full-text representations of file
- contents and property lists, emit only deltas of those
- items against their previous versions. This reduces (in
- some cases, drastically) the size of the dump file that
- <command>svnadmin dump</command> creates. There are, however,
- disadvantages to using this option—deltified
- dump files are more CPU-intensive to create, cannot be
- operated on by <command>svndumpfilter</command>, and tend
- not to compress as well as their nondeltified counterparts
- when using third-party tools such as <command>gzip</command>
- and <command>bzip2</command>.</para>
- </refsect1>
- <refsect1>
- <title>Options</title>
+ <para>The second useful option is <option>--deltas</option>.
+ This option causes <command>svnadmin dump</command> to,
+ instead of emitting full-text representations of file
+ contents and property lists, emit only deltas of those
+ items against their previous versions. This reduces (in
+ some cases, drastically) the size of the dump file that
+ <command>svnadmin dump</command> creates. There are, however,
+ disadvantages to using this option—deltified
+ dump files are more CPU-intensive to create, cannot be
+ operated on by <command>svndumpfilter</command>, and tend
+ not to compress as well as their nondeltified counterparts
+ when using third-party tools such as <command>gzip</command>
+ and <command>bzip2</command>.</para>
+ </refsect1>
+ <refsect1>
+ <title>Options</title>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
<xref linkend="svn.ref.svnadmin.sw.deltas" />
<xref linkend="svn.ref.svnadmin.sw.incremental" />
<xref linkend="svn.ref.svnadmin.sw.memory_cache_size" />
<xref linkend="svn.ref.svnadmin.sw.quiet" />
<xref linkend="svn.ref.svnadmin.sw.revision" />
</screen>
- </informalexample>
- </refsect1>
-
- <refsect1>
- <title>Examples</title>
+ </informalexample>
+ </refsect1>
+
+ <refsect1>
+ <title>Examples</title>
- <para>Dump your whole repository:</para>
+ <para>Dump your whole repository:</para>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
$ svnadmin dump /var/svn/repos > full.dump
* Dumped revision 0.
* Dumped revision 1.
* Dumped revision 2.
…
</screen>
- </informalexample>
+ </informalexample>
- <para>Incrementally dump a single transaction from your
- repository:</para>
+ <para>Incrementally dump a single transaction from your
+ repository:</para>
- <informalexample>
- <screen>
+ <informalexample>
+ <screen>
$ svnadmin dump /var/svn/repos -r 21 --incremental > incr.dump
* Dumped revision 21.
</screen>
- </informalexample>
+ </informalexample>
- </refsect1>
- </refentry>
+ </refsect1>
+ </refentry>
- <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
- <refentry id="svn.ref.svnadmin.c.help">
+ <!-- =============================================================== -->
+ <refentry id="svn.ref.svnadmin.c.help">
- <indexterm>
- <primary>svnadmin</primary>
- <secondary>subcommands</secondary>
- <tertiary>help</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>help</tertiary>
+ </indexterm>
- <refnamediv>
- <refname>svnadmin help (h, ?)</refname>
- <refpurpose>Help!</refpurpose>
- </refnamediv>
- <refsect1>
- <title>Synopsis</title>
- <para><literal>svnadmin help [SUBCOMMAND...]</literal></para>
- </refsect1>
+ <refnamediv>
+ <refname>svnadmin help (h, ?)</refname>
+ <refpurpose>Help!</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svnadmin help [SUBCOMMAND...]</literal></para>
+ </refsect1>
- <refsect1>
- <title>Description</title>
+ <refsect1>
+ <title>Description</title>
- <para>This subcommand is useful when you're trapped on a
- desert island with neither a Net connection nor a copy of
- this book.</para>
- </refsect1>
+ <para>This subcommand is useful when you're trapped on a
***The diff for this file has been truncated for email.***
More information about the svnbook-dev
mailing list