[svnbook] r4000 committed - Merge from trunk/en r3999, whose log message read like so:...

[svnbook at googlecode.com]

Revision: 4000
Author:   cmpilato at gmail.com
Date:     Mon Aug 15 12:29:10 2011
Log:      Merge from trunk/en r3999, whose log message read like so:

    * en/book/ch03-advanced-topics.xml
      Add a note that explains why 'svn update --set-depth exclude'
      doesn't look like a regular update.

http://code.google.com/p/svnbook/source/detail?r=4000

Modified:
  /branches/1.6/en
  /branches/1.6/en/book/ch03-advanced-topics.xml

=======================================
--- /branches/1.6/en/book/ch03-advanced-topics.xml	Mon Aug 15 12:19:55 2011
+++ /branches/1.6/en/book/ch03-advanced-topics.xml	Mon Aug 15 12:29:10 2011
@@ -2705,6 +2705,17 @@
        is too large to fit on your disk (which might, after all, be the
        very reason you don't want it in your working copy).</para>

+    <note>
+      <para>While the functionality for excluding an existing item
+        from a working copy was hung off of the <command>svn
+        update</command> command, you might have noticed that the
+        output from <userinput>svn update --set-depth
+        exclude</userinput> differs from that of a normal update
+        operation.  This output betrays the fact that, under the hood,
+        exlusion is a completely client-side operation, very much
+        unlike a typical update.</para>
+    </note>
+
      <para>In such a situation, you might consider a compromise
        approach.  First, check out the top-level directory
        with <option>--depth immediates</option>.  Then, exclude the