[svnbook] r4041 committed - Finish issue #120 ("1.7 change: New 'svn upgrade' subcommand")....
svnbook at googlecode.com
svnbook at googlecode.com
Mon Aug 29 11:12:15 CDT 2011
Revision: 4041
Author: cmpilato at gmail.com
Date: Mon Aug 29 09:11:02 2011
Log: Finish issue #120 ("1.7 change: New 'svn upgrade' subcommand").
* en/book/ch09-reference.xml
(svn.ref.svn.c.upgrade): New section.
http://code.google.com/p/svnbook/source/detail?r=4041
Modified:
/trunk/en/book/ch09-reference.xml
=======================================
--- /trunk/en/book/ch09-reference.xml Fri Aug 26 08:14:22 2011
+++ /trunk/en/book/ch09-reference.xml Mon Aug 29 09:11:02 2011
@@ -5575,8 +5575,107 @@
</refsect1>
</refentry>
+
+ <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-->
+ <refentry id="svn.ref.svn.c.upgrade">
+
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>upgrade</tertiary>
+ </indexterm>
+
+ <refnamediv>
+ <refname>svn upgrade</refname>
+ <refpurpose>Upgrade the metadata storage format for a
+ working copy.</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Synopsis</title>
+ <para><literal>svn upgrade [PATH...]</literal></para>
+ </refsect1>
+ <refsect1>
+ <title>Description</title>
+
+ <para>As new versions of Subversion are released, the format
+ used for the working copy metadata changes to accomodate
+ new features or fix bugs. Older versions of Subversion
+ would automatically upgrade working copies to the new
+ format the first time the working copy was used by the new
+ version of the software. Beginning with Subversion 1.7,
+ working copy upgrades must be explicitly performed at the
+ user's request. <command>svn upgrade</command> is the
+ subcommand used to trigger that upgrade process.</para>
+ </refsect1>
+
+ <refsect1>
+ <title>Options</title>
+
+ <informalexample>
+ <screen>
+--quiet (-q)
+</screen>
+ </informalexample>
+ </refsect1>
+
+ <refsect1>
+ <title>Examples</title>
+
+ <para>If you attempt to use Subversion 1.7 on a working copy
+ created with an older version of Subversion, you will see
+ an error:</para>
+
+ <informalexample>
+ <screen>
+$ svn status
+svn: E155036: Please see the 'svn upgrade' command
+svn: E155036: Working copy '/home/cmpilato/tests/wc' is too old (format
10, cr
+eated by Subversion 1.6)
+$
+</screen>
+ </informalexample>
+
+ <para>Use the <command>svn upgrade</command> command to
+ upgrade the working copy to the most recent metadata
+ format supported by your version of Subversion.</para>
+
+ <informalexample>
+ <screen>
+$ svn upgrade
+Upgraded '.'
+Upgraded 'A'
+Upgraded 'A/B'
+Upgraded 'A/B/E'
+Upgraded 'A/B/F'
+Upgraded 'A/C'
+Upgraded 'A/D'
+Upgraded 'A/D/G'
+Upgraded 'A/D/H'
+$ svn status
+D A/B/E/alpha
+M A/D/gamma
+A A/newfile
+$
+</screen>
+ </informalexample>
+
+ <para>Notice that <command>svn upgrade</command> preserved
+ the local modifications present in the working copy at the
+ time of the upgrade, which were introduced by the version
+ of Subversion previously used to manipulate this working
+ copy.</para>
+
+ <warning>
+ <para>As was the case with automatically upgraded working
+ copies in the past, explicitly upgraded working copies
+ will be unusable by older versions of Subversion,
+ too.</para>
+ </warning>
+
+ </refsect1>
+ </refentry>
+
</sect2>
-
</sect1>
<!-- =================================================================
-->
More information about the svnbook-dev
mailing list