[svnbook] r3867 committed - Finish Issue #13 ("Spaces in file names in svn:externals")....
svnbook at googlecode.com
svnbook at googlecode.com
Thu Jun 30 13:20:59 CDT 2011
Author: cmpilato at gmail.com
Date: Thu Jun 30 11:20:09 2011
Log: Finish Issue #13 ("Spaces in file names in svn:externals").
(svn.advanced.externals): Document the quoting/escape mechanism for
external working copies.
--- /trunk/src/en/book/ch03-advanced-topics.xml Thu Jun 30 09:57:00 2011
+++ /trunk/src/en/book/ch03-advanced-topics.xml Thu Jun 30 11:20:09 2011
@@ -3097,13 +3097,33 @@
/skinproj at 148 third-party/skins
//svn.example.com/skin-maker at 21 third-party/skins/toolkit
- <para>Subversion 1.6 brings another improvement to externals
- definitions by introducing external definitions for files.
- <firstterm>File externals</firstterm> are configured just
- like externals for directories and appear as a versioned
- file in the working copy.</para>
+ <para>Subversion 1.6 brings two more improvements to externals
+ definitions. First, it adds a quoting and escape mechanism to
+ the syntax so that the path of the external working copy may
+ contain whitespace. This was previously problematic, of course,
+ because whitespace is used to delimit the fields in an externals
+ definition. Now you need only wrap such a path specification in
+ double-quote (<literal>"<!-- " --></literal>) characters or
+ escape the problematic characters in the path with a backslash
+ (<literal>\</literal>) character. Of course, if you have spaces
+ in the <emphasis>URL</emphasis> portion of the external
+ definition, you should use the standard URI-encoding mechanism
+ to represent those.</para>
+$ svn propget svn:externals paint
+http://svn.thirdparty.com/repos/My%20Project "My Project"
+http://svn.thirdparty.com/repos/%22Quotes%20Too%22 \"Quotes\ Too\"
+ <para>Subversion 1.6 also introduces support for external
+ definitions for files. <firstterm>File externals</firstterm>
+ are configured just like externals for directories and appear as
+ a versioned file in the working copy.</para>
<para>For example, let's say you had the file
<filename>/trunk/bikeshed/blue.html</filename> in your repository,
@@ -3113,6 +3133,7 @@
<para>The externals definition required to achieve this should
look familiar by now:</para>
$ svn propget svn:externals www/
^/trunk/bikeshed/blue.html at 40 green.html
@@ -3124,6 +3145,7 @@
Update to revision 103.
$ svn status
<para>As you can see in the previous output, Subversion denotes file
@@ -3156,6 +3178,7 @@
Last Changed Date: 2009-07-20 20:38:20 +0100 (Mon, 20 Jul 2009)
Text Last Updated: 2009-07-20 23:22:36 +0100 (Mon, 20 Jul 2009)
<para>Because file externals appear in the working copy as
@@ -3173,6 +3196,7 @@
svn: Commit failed (details follow):
svn: File '/trunk/bikeshed/blue.html' is out of date
<para>Keep this in mind when defining file externals.
More information about the svnbook-dev