[svnbook commit] r3247 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Wed Aug 6 03:58:40 CDT 2008
Author: cmpilato
Date: Wed Aug 6 03:58:39 2008
New Revision: 3247
Log:
* src/en/book/ch09-reference.xml
* src/en/book/appb-svn-for-cvs-users.xml
* src/en/book/ch05-repository-admin.xml
* src/en/book/ch06-server-configuration.xml
Consistify! Refer to 'dump file' or 'dump stream', not 'dumpfile'
or 'dumpstream'. And wrap instances of stdin, stdout, and stderr
with <filename> tags (instead of a mix of filename, literal, and
emphasis tags).
Modified:
trunk/src/en/book/appb-svn-for-cvs-users.xml
trunk/src/en/book/ch05-repository-admin.xml
trunk/src/en/book/ch06-server-configuration.xml
trunk/src/en/book/ch09-reference.xml
Modified: trunk/src/en/book/appb-svn-for-cvs-users.xml
==============================================================================
--- trunk/src/en/book/appb-svn-for-cvs-users.xml (original)
+++ trunk/src/en/book/appb-svn-for-cvs-users.xml Wed Aug 6 03:58:39 2008
@@ -553,7 +553,7 @@
it scans your CVS repository multiple times and attempts to
deduce commits, branches, and tags as best it can. When it
finishes, the result is either a Subversion repository or a
- portable Subversion dumpfile representing your code's history.
+ portable Subversion dump file representing your code's history.
See the web site for detailed instructions and caveats.</para>
</sect1>
Modified: trunk/src/en/book/ch05-repository-admin.xml
==============================================================================
--- trunk/src/en/book/ch05-repository-admin.xml (original)
+++ trunk/src/en/book/ch05-repository-admin.xml Wed Aug 6 03:58:39 2008
@@ -1799,7 +1799,7 @@
<para>Subversion provides such functionality by way of
<firstterm>repository dump streams</firstterm>. A repository
- dump stream (often referred to as a <quote>dumpfile</quote>
+ dump stream (often referred to as a <quote>dump file</quote>
when stored as a file on disk) is a portable, flat file format
that describes the various revisions in your
repository—what was changed, by whom, when, and so on.
Modified: trunk/src/en/book/ch06-server-configuration.xml
==============================================================================
--- trunk/src/en/book/ch06-server-configuration.xml (original)
+++ trunk/src/en/book/ch06-server-configuration.xml Wed Aug 6 03:58:39 2008
@@ -543,8 +543,8 @@
<para>When invoked with the <option>--inetd</option> option,
<command>svnserve</command> attempts to speak with a
- Subversion client via <emphasis>stdin</emphasis> and
- <emphasis>stdout</emphasis> using a custom protocol. This is
+ Subversion client via <filename>stdin</filename> and
+ <filename>stdout</filename> using a custom protocol. This is
the standard behavior for a program being run via
<command>inetd</command>. The IANA has reserved port 3690 for
the Subversion protocol, so on a Unix-like system you can add
@@ -591,7 +591,7 @@
the command line; instead, the SSH daemon
does so for you.) The <command>svnserve</command> program
behaves normally (communicating via
- <emphasis>stdin</emphasis> and <emphasis>stdout</emphasis>)
+ <filename>stdin</filename> and <filename>stdout</filename>)
and assumes that the traffic is being automatically
redirected over some sort of tunnel back to the client.
When <command>svnserve</command> is invoked by a tunnel
Modified: trunk/src/en/book/ch09-reference.xml
==============================================================================
--- trunk/src/en/book/ch09-reference.xml (original)
+++ trunk/src/en/book/ch09-reference.xml Wed Aug 6 03:58:39 2008
@@ -5677,7 +5677,7 @@
<refnamediv>
<refname>svnadmin dump</refname>
- <refpurpose>Dump the contents of the filesystem to <literal>stdout</literal>.</refpurpose>
+ <refpurpose>Dump the contents of the filesystem to <filename>stdout</filename>.</refpurpose>
</refnamediv>
<refsect1>
<title>Synopsis</title>
@@ -5686,9 +5686,9 @@
<refsect1>
<title>Description</title>
- <para>Dump the contents of the filesystem to <literal>stdout</literal> in a
- <quote>dumpfile</quote> portable format, sending feedback
- to <literal>stderr</literal>. Dump revisions
+ <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
@@ -5696,7 +5696,7 @@
revision tree. See <xref linkend="svn.reposadmin.maint.migrate"/>
for a practical use.</para>
- <para>By default, the Subversion dumpfile stream contains a
+ <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
@@ -5705,18 +5705,18 @@
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 dumpfile; for a
+ its properties, are presented in the dump file; for a
directory, all of its properties are presented.</para>
- <para>Two useful options modify the dumpfile
+ <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 dumpfile stream to contain only
+ 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 dumpfile is presented. This is useful for generating
- a relatively small dumpfile to be loaded into another
+ 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>
@@ -5725,10 +5725,10 @@
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 dumpfile that
+ some cases, drastically) the size of the dump file that
<command>svnadmin dump</command> creates. There are, however,
disadvantages to using this option—deltified
- dumpfiles are more CPU-intensive to create, cannot be
+ 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>
@@ -5944,8 +5944,8 @@
<refnamediv>
<refname>svnadmin load</refname> <refpurpose>Read a
- <quote>dumpfile</quote>-formatted stream from
- <literal>stdin</literal>.</refpurpose>
+ repository dump stream from
+ <filename>stdin</filename>.</refpurpose>
</refnamediv>
<refsect1>
<title>Synopsis</title>
@@ -5954,9 +5954,9 @@
<refsect1>
<title>Description</title>
- <para>Read a <quote>dumpfile</quote>-formatted stream from
- <literal>stdin</literal>, committing new revisions into the repository's
- filesystem. Send progress feedback to <literal>stdout</literal>.</para>
+ <para>Read a repository dump stream from
+ <filename>stdin</filename>, committing new revisions into the repository's
+ filesystem. Send progress feedback to <filename>stdout</filename>.</para>
</refsect1>
<refsect1>
@@ -8073,7 +8073,7 @@
<term><option>--inetd</option> (<option>-i</option>)</term>
<listitem>
<para>Causes <command>svnserve</command> to use the
- <literal>stdin</literal>/<literal>stdout</literal> file descriptors, as is appropriate for a
+ <filename>stdin</filename> and <filename>stdout</filename> file descriptors, as is appropriate for a
daemon running out of <command>inetd</command>.</para>
</listitem>
</varlistentry>
@@ -8153,7 +8153,7 @@
<para>Causes <command>svnserve</command> to run in tunnel
mode, which is just like the <command>inetd</command>
mode of operation (both modes serve one connection over
- <literal>stdin</literal>/<literal>stdout</literal>, and then exit), except that the connection
+ <filename>stdin</filename>/<filename>stdout</filename>, and then exit), except that the connection
is considered to be preauthenticated with the username
of the current UID. This flag is automatically passed
for you by the client when running over a tunnel agent
@@ -8202,7 +8202,7 @@
<title>svndumpfilter</title>
<para><command>svndumpfilter</command> is a command-line utility
- for removing history from a Subversion dumpfile by either
+ for removing history from a Subversion dump file by either
excluding or including paths beginning with one or more named
prefixes. For details, see
<xref linkend="svn.reposadmin.maint.tk.svndumpfilter"/>.</para>
@@ -8222,7 +8222,7 @@
<listitem>
<para>If filtering causes any revision to be empty (i.e.,
causes no change to the repository), removes these
- revisions from the final dumpfile.</para>
+ revisions from the final dump file.</para>
</listitem>
</varlistentry>
@@ -8287,7 +8287,7 @@
<refnamediv>
<refname>svndumpfilter exclude</refname>
- <refpurpose>Filter out nodes with given prefixes from the dumpstream.</refpurpose>
+ <refpurpose>Filter out nodes with given prefixes from the dump stream.</refpurpose>
</refnamediv>
<refsect1>
<title>Synopsis</title>
@@ -8298,7 +8298,7 @@
<para>This can be used to exclude nodes that begin with one or
more <replaceable>PATH_PREFIX</replaceable>es from a
- filtered dumpfile.</para>
+ filtered dump file.</para>
</refsect1>
<refsect1>
@@ -8316,7 +8316,7 @@
<refsect1>
<title>Examples</title>
- <para>If we have a dumpfile from a repository with a number of
+ <para>If we have a dump file from a repository with a number of
different picnic-related directories in it, but we want to keep
everything <emphasis>except</emphasis>
the <filename>sandwiches</filename> part of the repository,
@@ -8351,7 +8351,7 @@
<refnamediv>
<refname>svndumpfilter include</refname>
<refpurpose>Filter out nodes without given prefixes from
- dumpstream.</refpurpose>
+ dump stream.</refpurpose>
</refnamediv>
<refsect1>
<title>Synopsis</title>
@@ -8362,7 +8362,7 @@
<para>Can be used to include nodes that begin with one or
more <replaceable>PATH_PREFIX</replaceable>es in a
- filtered dumpfile (thus excluding all other paths).</para>
+ filtered dump file (thus excluding all other paths).</para>
</refsect1>
<refsect1>
@@ -8380,7 +8380,7 @@
<refsect1>
<title>Example</title>
- <para>If we have a dumpfile from a repository with a number of
+ <para>If we have a dump file from a repository with a number of
different picnic-related directories in it, but only want to
keep only the <filename>sandwiches</filename> part of the
repository, we'll include only that path:</para>
@@ -9355,7 +9355,7 @@
nonzero exit status, the commit <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
- to <literal>stderr</literal> will be marshalled back to the
+ to <filename>stderr</filename> will be marshalled back to the
client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -9412,7 +9412,7 @@
<para>If the <literal>pre-revprop-change</literal> hook
doesn't exist, isn't executable, or returns a nonzero exit
value, no change to the property will be made, and anything
- printed to <literal>stderr</literal> is marshalled back to the client.</para>
+ printed to <filename>stderr</filename> is marshalled back to the client.</para>
</refsect1>
@@ -9487,7 +9487,7 @@
nonzero exit status, the change <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
- to <literal>stderr</literal> will be marshalled back to the
+ to <filename>stderr</filename> will be marshalled back to the
client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -9557,7 +9557,7 @@
<para>If the <literal>pre-lock</literal> hook program returns
a nonzero exit value, the lock action is aborted and
- anything printed to <literal>stderr</literal> is marshalled back to the
+ anything printed to <filename>stderr</filename> is marshalled back to the
client.</para>
</refsect1>
@@ -9614,7 +9614,7 @@
nonzero exit status, the lock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
- to <literal>stderr</literal> will be marshalled back to the
+ to <filename>stderr</filename> will be marshalled back to the
client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -9675,7 +9675,7 @@
<para>If the <literal>pre-unlock</literal> hook program
returns a nonzero exit value, the unlock action is aborted
- and anything printed to <literal>stderr</literal> is marshalled back to the
+ and anything printed to <filename>stderr</filename> is marshalled back to the
client.</para>
</refsect1>
@@ -9732,7 +9732,7 @@
nonzero exit status, the unlock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
- to <literal>stderr</literal> will be marshalled back to the
+ to <filename>stderr</filename> will be marshalled back to the
client, making it easier to diagnose hook failures.</para>
</refsect1>
More information about the svnbook-dev
mailing list