[svnbook commit] r3199 - in trunk/src/nb: . book
sunny256
noreply at red-bean.com
Tue Jul 15 04:03:57 CDT 2008
Author: sunny256
Date: Tue Jul 15 04:03:57 2008
New Revision: 3199
Log:
Sync the Norwegian and English book up to r2625.
* src/nb/book/ch-reference.xml
* src/nb/book/ch-advanced-topics.xml
Merged and updated r2614, r2615, r2616, r2617, r2618, r2623, r2625.
* src/nb/LAST_SYNC
Updated by "make sync HEAD=2625".
* src/nb/TRANSLATION-STATUS
Updated by "make status".
Modified:
trunk/src/nb/LAST_SYNC
trunk/src/nb/TRANSLATION-STATUS
trunk/src/nb/book/ch-advanced-topics.xml
trunk/src/nb/book/ch-reference.xml
Modified: trunk/src/nb/LAST_SYNC
==============================================================================
--- trunk/src/nb/LAST_SYNC (original)
+++ trunk/src/nb/LAST_SYNC Tue Jul 15 04:03:57 2008
@@ -1 +1 @@
-2613
+2625
Modified: trunk/src/nb/TRANSLATION-STATUS
==============================================================================
--- trunk/src/nb/TRANSLATION-STATUS (original)
+++ trunk/src/nb/TRANSLATION-STATUS Tue Jul 15 04:03:57 2008
@@ -18,8 +18,8 @@
* book/ch-basic-usage.xml
Untranslated: 4.31% - 108 lines in 8 blocks
* book/ch-advanced-topics.xml
- Untranslated: 76.53% - 2133 lines in 8 blocks
- Need proofreading: 19.50% - 577 lines in 2 blocks
+ Untranslated: 77.06% - 2157 lines in 8 blocks
+ Need proofreading: 18.98% - 567 lines in 2 blocks
* book/ch-branching-and-merging.xml
Untranslated: 5.06% - 125 lines in 1 block
Need proofreading: 10.22% - 242 lines in 1 block
@@ -34,7 +34,7 @@
* book/ch-developer-info.xml
Untranslated: 100.00% - 1427 lines in 1 block
* book/ch-reference.xml
- Untranslated: 100.00% - 6485 lines in 1 block
+ Untranslated: 100.00% - 6917 lines in 1 block
* book/app-quickstart.xml
Translation complete
* book/app-svn-for-cvs-users.xml
@@ -49,4 +49,4 @@
* book/index.xml
Translation complete
-Summa summarum: 58.35% translated, 17.14% need proofreading
+Summa summarum: 57.75% translated, 16.93% need proofreading
Modified: trunk/src/nb/book/ch-advanced-topics.xml
==============================================================================
--- trunk/src/nb/book/ch-advanced-topics.xml (original)
+++ trunk/src/nb/book/ch-advanced-topics.xml Tue Jul 15 04:03:57 2008
@@ -1137,11 +1137,11 @@
</screen>
<!-- @ENGLISH {{{
- <para>You need to use the <command>propdel</command> command to
- delete properties altogether. The syntax is similar to the
+ <para>You need to use the <command>propdel</command> subcommand
+ to delete properties altogether. The syntax is similar to the
other property commands:</para>
@ENGLISH }}} -->
- <para>Du må bruke <command>propdel</command>-kommandoen for å
+ <para>Du må bruke <command>propdel</command>-delkommandoen for å
fjerne egenskaper helt.
Syntaksen er lik de andre egenskapskommandoene:</para>
@@ -1509,27 +1509,6 @@
laget av <command>svn diff</command>, må forandringer i
egenskaper legges til for hånd.</para>
- <!-- @ENGLISH {{{
- <para>As you can see, the presence of property modifications has
- no outstanding effect on the typical Subversion workflow.
- Your general patterns of updating your working copy, checking
- the status of your files and directories, reporting on the
- modifications you have made, and committing those
- modifications to the repository are completely immune to the
- presence or absence of properties. The <command>svn</command>
- program has some additional subcommands for actually making
- property changes, but that is the only noticeable asymmetry.</para>
- @ENGLISH }}} -->
- <para>Som du ser, påvirkes ikke arbeidsflyten i Subversion
- nevneverdig selv om egenskapene er forandret.
- Rutinen med å oppdatere arbeidskopien, sjekke status på filer og
- kataloger, rapportering om forandringer som du har gjort og
- innlegging av disse forandringene til depotetet er fullstendig
- likegyldig til nærværet eller fraværet av egenskaper.
- <command>svn</command>-programmet har noen tilleggskommandoer
- for å faktisk gjøre forandringer i egenskaper, men det er den
- eneste merkbare forskjellen.</para>
-
</sect2>
<!-- @CHK }} -->
@@ -1634,67 +1613,76 @@
<sect2 id="svn.advanced.props.special.mime-type">
<title>File Content Type</title>
- <para>Software programs on most modern operating systems make
- assumptions about the type and format of the contents of a
- file by the file's name, specifically its file extension. For
- example, files whose names end in <filename>.txt</filename>
- are generally assumed to be human-readable, able to be
- understood by simple perusal rather than requiring complex
- processing to decipher. Files whose names end in
- <filename>.png</filename>, on the other hand, are assumed to
- be of the Portable Network Graphics type—not
- human-readable at all, and sensible only when interpreted by
- software which understands the PNG format and can render the
- information in that format as a raster image.</para>
-
- <para>Unfortunately, some of those extensions have changed
- meanings over time. When personal computers first appeared, a
- file named <filename>README.DOC</filename> would have almost
- certainly been a plaintext file, just like today's
- <filename>.txt</filename> files. But by the mid-1990's,
- you could almost bet that a file of that name would not be a
- plaintext file at all, but instead a Microsoft Word document
- with a proprietary, non-human-readable format. But this
- change didn't occur overnight—there was certainly a
- period of confusion for computer users over what exactly they
- had in hand when they saw a <filename>.DOC</filename> file.
- <footnote>
- <para>You think that was rough? During that same era,
- WordPerfect also used <filename>.DOC</filename> for their
- proprietary file format's preferred extension!</para>
- </footnote>
- </para>
+ <para>Subversion joins the ranks of the many applications which
+ recognize and make use of Multipurpose Internet Mail
+ Extensions (MIME) content types. Besides being a
+ general-purpose storage location for a file's content type,
+ the value of the <literal>svn:mime-type</literal> file
+ property determines some behavioral characteristics of
+ Subversion itself.</para>
- <para>The popularity of computer networking cast still more
- doubt on the mapping between a file's name and its content.
- With information being served across networks and generated
- dynamically by server-side scripts, there was often no real
- file <foreignphrase>per se</foreignphrase> to speak of, and
- therefore no file name. Web servers, for example, needed some
- other way to tell browsers what they were downloading so the
- browser could do something intelligent with that information,
- whether that was to display the data using a program
- registered to handle that data type, or to prompt the user for
- where on the client machine to store the downloaded
- data.</para>
-
- <para>Eventually, a standard emerged for, among other things,
- describing the contents of a data stream. In 1996, RFC2045
- was published, the first of five RFCs describing Multipurpose
- Internet Mail Extensions (MIME). In it, this RFC describes
- the concept of media types and subtypes, and recommends a
- syntax for the representation of those types. Today, MIME
- media types—or, MIME types— are used almost
- universally across e-mail applications, Web servers, and other
- software as the <foreignphrase>de facto</foreignphrase>
- mechanism for clearing up the file content confusion.</para>
-
- <para>Subversion joins the ranks of applications which recognize
- and make use of MIME types. Besides being a general-purpose
- storage location for a file's content type, the value of the
- <literal>svn:mime-type</literal> file property determines some
- behavioral characteristics of Subversion itself.</para>
+ <sidebar>
+ <title>Identifying File Types</title>
+
+ <para>Software programs on most modern operating systems make
+ assumptions about the type and format of the contents of a
+ file by the file's name, specifically its file extension.
+ For example, files whose names end in
+ <filename>.txt</filename> are generally assumed to be
+ human-readable, able to be understood by simple perusal
+ rather than requiring complex processing to decipher. Files
+ whose names end in <filename>.png</filename>, on the other
+ hand, are assumed to be of the Portable Network Graphics
+ type—not human-readable at all, and sensible only when
+ interpreted by software which understands the PNG format and
+ can render the information in that format as a raster
+ image.</para>
+
+ <para>Unfortunately, some of those extensions have changed
+ meanings over time. When personal computers first appeared,
+ a file named <filename>README.DOC</filename> would have
+ almost certainly been a plaintext file, just like today's
+ <filename>.txt</filename> files. But by the mid-1990's, you
+ could almost bet that a file of that name would not be a
+ plaintext file at all, but instead a Microsoft Word document
+ with a proprietary, non-human-readable format. But this
+ change didn't occur overnight—there was certainly a
+ period of confusion for computer users over what exactly
+ they had in hand when they saw a <filename>.DOC</filename>
+ file.
+ <footnote>
+ <para>You think that was rough? During that same era,
+ WordPerfect also used <filename>.DOC</filename> for their
+ proprietary file format's preferred extension!</para>
+ </footnote>
+ </para>
+
+ <para>The popularity of computer networking cast still more
+ doubt on the mapping between a file's name and its content.
+ With information being served across networks and generated
+ dynamically by server-side scripts, there was often no real
+ file <foreignphrase>per se</foreignphrase> to speak of, and
+ therefore no file name. Web servers, for example, needed
+ some other way to tell browsers what they were downloading
+ so the browser could do something intelligent with that
+ information, whether that was to display the data using a
+ program registered to handle that data type, or to prompt
+ the user for where on the client machine to store the
+ downloaded data.</para>
+
+ <para>Eventually, a standard emerged for, among other things,
+ describing the contents of a data stream. In 1996, RFC2045
+ was published, the first of five RFCs describing MIME. In
+ it, this RFC describes the concept of media types and
+ subtypes, and recommends a syntax for the representation of
+ those types. Today, MIME media types—or, MIME
+ types— are used almost universally across e-mail
+ applications, Web servers, and other software as the
+ <foreignphrase>de facto</foreignphrase> mechanism for
+ clearing up the file content confusion.</para>
+ </sidebar>
+
<para>For example, one of the benefits that Subversion typically
provides is contextual, line-based merging of changes received
from the server during an update into your working file. But
@@ -1891,7 +1879,7 @@
<!-- ================================================================= -->
<!-- ================================================================= -->
<sect1 id="svn.advanced.props.special.ignore">
- <title>Selective Versioning</title>
+ <title>Ignoring Unversioned Items</title>
<para>In any given working copy there is a good chance that
alongside all those versioned files and directories are other
@@ -1919,7 +1907,7 @@
directories—its output can get quite noisy where many of
these things exist.</para>
- <para>So Subversion provides a pair of ways for telling it which
+ <para>So Subversion provides two ways for telling it which
files you would prefer that it simply disregard. One of the
ways involves the use of Subversion's runtime configuration
system (see <xref linkend="svn.advanced.confarea" />), and
@@ -1967,7 +1955,7 @@
<para>Subversion's support for ignorable file patterns extends
only to the one-time process of adding unversioned
files and directories to version control. Once an object is
- under Subversion's watchkeep, the ignore pattern mechanisms no
+ under Subversion's control, the ignore pattern mechanisms no
longer apply to it. In other words, don't expect Subversion
to avoid committing changes you've made to a versioned file
simply because that file's name matches an ignore
@@ -2078,6 +2066,7 @@
<screen>
$ svn status --no-ignore
+ M calc
M calc/button.c
I calc/calculator
? calc/data.c
@@ -2564,7 +2553,7 @@
can cause a repository to be <quote>wedged</quote>, as
described in <xref linkend="svn.reposadmin.maint.recovery"/>.</para>
- <para>You can generally forget about these other sorts of lock,
+ <para>You can generally forget about these other kinds of locks
until something goes wrong that requires you to care about
them. In this book, <quote>lock</quote> means the first sort
unless the contrary is either clear from context or explicitly
@@ -3032,7 +3021,7 @@
something is strange when she opens the file for editing.
Many applications alert users immediately when a read-only
file is opened for editing. And nearly all applications would
- at least prevert her from saving changes to the file. This
+ at least prevent her from saving changes to the file. This
reminds her to lock the file before editing, whereby she
discovers the pre-existing lock:</para>
@@ -3105,7 +3094,7 @@
<firstterm>externals definitions</firstterm>. An externals
definition is a mapping of a local directory to the
URL—and possibly a particular revision—of a
- versioned object. In Subversion, you declare externals
+ versioned directory. In Subversion, you declare externals
definitions in groups using the <literal>svn:externals</literal>
property. You can create or modify this property using
<command>svn propset</command> or <command>svn
@@ -3263,9 +3252,23 @@
$
</screen>
- <para>Be aware, too, that if you need to re-parent your working
- copy (using <command>svn switch --relocate</command>), externals
- definitions will <emphasis>not</emphasis> also be
+ <para>Also, the fact that externals definitions use absolute URLs
+ can cause problems with repositories that are available via
+ multiple URL schemes. For example, if your Subversion server is
+ configured to allow everyone to checkout the repository over
+ <literal>http://</literal> or <literal>https://</literal>, but
+ only allow commits to come in via <literal>https://</literal>,
+ you have an interesting problem on your hands. If your
+ externals definitions use the <literal>http://</literal> form
+ of the repository URLs, you won't be able to commit anything
+ from the working copies created by those externals. On the
+ other hand, if they use the <literal>https://</literal> form of
+ the URLs, anyone who might be checking out via
+ <literal>http://</literal> because their client doesn't support
+ <literal>https://</literal> will be unable to fetch the external
+ items. Be aware, too, that if you need to re-parent your
+ working copy (using <command>svn switch --relocate</command>),
+ externals definitions will <emphasis>not</emphasis> also be
re-parented.</para>
<para>Finally, there might be times when you would prefer that
Modified: trunk/src/nb/book/ch-reference.xml
==============================================================================
--- trunk/src/nb/book/ch-reference.xml (original)
+++ trunk/src/nb/book/ch-reference.xml Tue Jul 15 04:03:57 2008
@@ -530,6 +530,13 @@
<title><command>svn</command> Subcommands</title>
<refentry id="svn.ref.svn.c.add">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>add</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn add</refname>
<refpurpose>Add files, directories, or symbolic links.</refpurpose>
@@ -629,6 +636,13 @@
</refentry>
<refentry id="svn.ref.svn.c.blame">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>blame</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn blame</refname>
<refpurpose>Show author and revision information in-line
@@ -692,6 +706,13 @@
</refentry>
<refentry id="svn.ref.svn.c.cat">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>cat</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn cat</refname>
<refpurpose>Output the contents of the specified files or
@@ -770,6 +791,13 @@
</refentry>
<refentry id="svn.ref.svn.c.checkout">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>checkout</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn checkout</refname>
<refpurpose>Check out a working copy from a repository.</refpurpose>
@@ -900,6 +928,13 @@
</refentry>
<refentry id="svn.ref.svn.c.cleanup">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>cleanup</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn cleanup</refname>
<refpurpose>Recursively clean up the working copy.</refpurpose>
@@ -971,6 +1006,13 @@
</refentry>
<refentry id="svn.ref.svn.c.commit">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>commit</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn commit</refname>
<refpurpose>Send changes from your working copy to the repository.</refpurpose>
@@ -1103,6 +1145,13 @@
</refentry>
<refentry id="svn.ref.svn.c.copy">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>copy</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn copy</refname>
<refpurpose>Copy a file or directory in a working copy or
@@ -1271,6 +1320,13 @@
</refentry>
<refentry id="svn.ref.svn.c.delete">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>delete</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn delete</refname>
<refpurpose>Delete an item from a working copy
@@ -1377,6 +1433,13 @@
</refentry>
<refentry id="svn.ref.svn.c.diff">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>diff</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn diff</refname>
<refpurpose>Display the differences between two paths.</refpurpose>
@@ -1622,6 +1685,13 @@
</refentry>
<refentry id="svn.ref.svn.c.export">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>export</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn export</refname>
<refpurpose>Export a clean directory tree.</refpurpose>
@@ -1729,6 +1799,13 @@
<refentry id="svn.ref.svn.c.help">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>help</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn help</refname>
<refpurpose>Help!</refpurpose>
@@ -1774,6 +1851,13 @@
</refentry>
<refentry id="svn.ref.svn.c.import">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>import</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn import</refname>
<refpurpose>Commit an unversioned file or tree into the
@@ -1869,6 +1953,13 @@
</refentry>
<refentry id="svn.ref.svn.c.info">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>info</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn info</refname>
<refpurpose>Display information about a local or remote
@@ -2023,6 +2114,13 @@
</refentry>
<refentry id="svn.ref.svn.c.list">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>list</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn list</refname>
<refpurpose>List directory entries in the repository.</refpurpose>
@@ -2129,6 +2227,13 @@
<refentry id="svn.ref.svn.c.lock">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>lock</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn lock</refname>
<refpurpose>Lock working copy paths or URLs in the
@@ -2223,6 +2328,13 @@
<refentry id="svn.ref.svn.c.log">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>log</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn log</refname>
<refpurpose>Display commit log messages.</refpurpose>
@@ -2460,6 +2572,13 @@
</refentry>
<refentry id="svn.ref.svn.c.merge">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>merge</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn merge</refname>
<refpurpose>Apply the differences between two sources to a
@@ -2574,6 +2693,13 @@
</refentry>
<refentry id="svn.ref.svn.c.mkdir">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>mkdir</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn mkdir</refname>
<refpurpose>Create a new directory under version control.</refpurpose>
@@ -2653,6 +2779,13 @@
</refentry>
<refentry id="svn.ref.svn.c.move">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>move</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn move</refname>
<refpurpose>Move a file or directory.</refpurpose>
@@ -2760,6 +2893,13 @@
</refentry>
<refentry id="svn.ref.svn.c.propdel">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>propdel</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn propdel</refname>
<refpurpose>Remove a property from an item.</refpurpose>
@@ -2831,6 +2971,13 @@
</refentry>
<refentry id="svn.ref.svn.c.propedit">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>propedit</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn propedit</refname>
<refpurpose>Edit the property of one or more items under
@@ -2900,6 +3047,13 @@
</refentry>
<refentry id="svn.ref.svn.c.propget">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>propget</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn propget</refname>
<refpurpose>Print the value of a property.</refpurpose>
@@ -2976,6 +3130,13 @@
</refentry>
<refentry id="svn.ref.svn.c.proplist">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>proplist</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn proplist</refname>
<refpurpose>List all properties.</refpurpose>
@@ -3056,6 +3217,13 @@
</refentry>
<refentry id="svn.ref.svn.c.propset">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>propset</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn propset</refname>
<refpurpose>Set PROPNAME to PROPVAL on files, directories, or revisions.</refpurpose>
@@ -3186,6 +3354,13 @@
</refentry>
<refentry id="svn.ref.svn.c.resolved">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>resolved</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn resolved</refname>
<refpurpose>Remove <quote>conflicted</quote> state on
@@ -3269,6 +3444,13 @@
</refentry>
<refentry id="svn.ref.svn.c.revert">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>revert</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn revert</refname>
<refpurpose>Undo all local edits.</refpurpose>
@@ -3366,6 +3548,13 @@
</refentry>
<refentry id="svn.ref.svn.c.status">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>status</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn status</refname>
<refpurpose>Print the status of working copy files and directories.</refpurpose>
@@ -3765,6 +3954,13 @@
</refentry>
<refentry id="svn.ref.svn.c.switch">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>switch</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn switch</refname>
<refpurpose>Update working copy to a different URL.</refpurpose>
@@ -3919,6 +4115,13 @@
<refentry id="svn.ref.svn.c.unlock">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>unlock</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn unlock</refname>
<refpurpose>Unlock working copy paths or URLs.</refpurpose>
@@ -4006,6 +4209,13 @@
<refentry id="svn.ref.svn.c.update">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>update</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svn update</refname>
<refpurpose>Update your working copy.</refpurpose>
@@ -4288,6 +4498,13 @@
<title><command>svnadmin</command> Subcommands</title>
<refentry id="svn.ref.svnadmin.c.create">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>create</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin create</refname>
<refpurpose>Create a new, empty repository.</refpurpose>
@@ -4344,6 +4561,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.deltify">
+
+ <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>
@@ -4377,6 +4601,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.dump">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>dump</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin dump</refname>
<refpurpose>Dump the contents of filesystem to stdout.</refpurpose>
@@ -4480,6 +4711,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.help">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>help</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin help</refname> <refpurpose>Help!</refpurpose>
</refnamediv>
@@ -4505,6 +4743,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.hotcopy">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>hotcopy</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin hotcopy</refname>
<refpurpose>Make a hot copy of a repository.</refpurpose>
@@ -4540,6 +4785,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.list-dblogs">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>list-dblogs</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin list-dblogs</refname> <refpurpose>Ask
Berkeley DB which log files exist for a given Subversion
@@ -4566,6 +4818,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.list-unused-dblogs">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>list-unused-dblogs</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin list-unused-dblogs</refname>
<refpurpose>Ask Berkeley DB which log files can be safely
@@ -4608,6 +4867,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.load">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>load</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin load</refname> <refpurpose>Read a
<quote>dumpfile</quote>-formatted stream from
@@ -4667,6 +4933,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.lslocks">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>lslocks</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin lslocks</refname>
<refpurpose>Print descriptions of all locks.</refpurpose>
@@ -4708,6 +4981,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.lstxns">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>lstxns</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin lstxns</refname>
<refpurpose>Print the names of all uncommitted transactions.</refpurpose>
@@ -4741,6 +5021,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.recover">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>recover</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin recover</refname>
@@ -4816,6 +5103,13 @@
<refentry id="svn.ref.svnadmin.c.rmlocks">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>rmlocks</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin rmlocks</refname>
<refpurpose>Unconditionally remove one or more locks from a
@@ -4855,6 +5149,13 @@
<refentry id="svn.ref.svnadmin.c.rmtxns">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>rmtxns</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin rmtxns</refname>
<refpurpose>Delete transactions from a repository.</refpurpose>
@@ -4903,6 +5204,13 @@
<refentry id="svn.ref.svnadmin.c.setlog">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>setlog</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin setlog</refname>
<refpurpose>Set the log-message on a revision.</refpurpose>
@@ -4956,6 +5264,13 @@
</refentry>
<refentry id="svn.ref.svnadmin.c.verify">
+
+ <indexterm>
+ <primary>svnadmin</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>verify</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnadmin verify</refname>
<refpurpose>Verify the data stored in the repository.</refpurpose>
@@ -5084,6 +5399,13 @@
<title><command>svnlook</command></title>
<refentry id="svn.ref.svnlook.c.author">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>author</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook author</refname>
<refpurpose>Print the author.</refpurpose>
@@ -5123,6 +5445,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.cat">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>cat</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook cat</refname>
<refpurpose>Print the contents of a file.</refpurpose>
@@ -5174,6 +5503,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.changed">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>changed</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook changed</refname>
<refpurpose>Print the paths that were changed.</refpurpose>
@@ -5266,6 +5602,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.date">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>date</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook date</refname>
<refpurpose>Print the datestamp.</refpurpose>
@@ -5305,6 +5648,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.diff">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>diff</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook diff</refname>
<refpurpose>Print differences of changed files and properties.</refpurpose>
@@ -5369,6 +5719,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.dirs-changed">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>dirs-changed</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook dirs-changed</refname>
<refpurpose>Print the directories that were themselves changed.</refpurpose>
@@ -5409,6 +5766,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.help">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>help</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook help</refname> <refpurpose>Help!</refpurpose>
</refnamediv>
@@ -5433,6 +5797,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.history">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>history</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook history</refname>
<refpurpose>Print information about the history of a path in
@@ -5491,6 +5862,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.info">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>info</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook info</refname>
<refpurpose>Print the author, datestamp, log message size,
@@ -5535,6 +5913,13 @@
<refentry id="svn.ref.svnlook.c.lock">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>lock</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook lock</refname>
<refpurpose>If a lock exists on a path in the repository,
@@ -5580,6 +5965,13 @@
<refentry id="svn.ref.svnlook.c.log">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>log</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook log</refname>
<refpurpose>Print the log message.</refpurpose>
@@ -5618,6 +6010,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.propget">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>propget</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook propget</refname>
<refpurpose>Print the raw value of a property on a path in
@@ -5666,6 +6065,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.proplist">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>proplist</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook proplist</refname>
<refpurpose>Print the names and values of versioned file and
@@ -5725,6 +6131,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.tree">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>tree</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook tree</refname>
<refpurpose>Print the tree.</refpurpose>
@@ -5772,6 +6185,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.uuid">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>uuid</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook uuid</refname>
<refpurpose>Print the repository's
@@ -5804,6 +6224,13 @@
</refentry>
<refentry id="svn.ref.svnlook.c.youngest">
+
+ <indexterm>
+ <primary>svnlook</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>youngest</tertiary>
+ </indexterm>
+
<refnamediv>
<refname>svnlook youngest</refname>
<refpurpose>Print the youngest revision number.</refpurpose>
@@ -6003,6 +6430,11 @@
<title><command>svnversion</command></title>
<refentry id="svn.ref.svnversion.re">
+
+ <indexterm>
+ <primary>svnversion</primary>
+ </indexterm>
+
<refnamediv>
<refname>svnversion</refname>
<refpurpose>Summarize the local revision(s) of a working
More information about the svnbook-dev
mailing list