Issue 94 in svnbook: Document that svn:externals update behaves differently within and outside imported directory

[svnbook at googlecode.com]

Updates:
	Status: Fixed
	Labels: Milestone-en-1.6

Comment #2 on issue 94 by cmpilato: Document that svn:externals update  
behaves differently within and outside imported directory
http://code.google.com/p/svnbook/issues/detail?id=94

I added the following as a warning in the Externals Definitions section:

"External working copies are still completely self-sufficient working  
copies. You can operate directly on them as you would any other working  
copy. This can be a handy feature, allowing you to examine an external  
working copy independently of any primary working copy whose svn:externals  
property caused its instantiation. Be careful, though, that you don't  
inadvertently modify your external working copy in subtle ways that cause  
problems. For example, while an externals definition might specify that the  
external working copy should be held at a particular revision number, if  
you run svn update directly on the external working copy, Subversion will  
oblige, and now your external working copy is out of sync with its  
declaration in the primary working copy. Using svn switch to directly  
switch the external working copy (or some portion thereof) to another URL  
could cause similar problems if the contents of the primary working copy  
are expecting particular contents in the external content."

Thanks for the suggestion.