[svnbook commit] r1288 - in trunk/src/en: . book

fitz svnbook-dev at red-bean.com
Mon May 16 09:54:23 CDT 2005

Author: fitz
Date: Mon May 16 09:54:21 2005
New Revision: 1288

Knock out a TODO task.

* src/en/book/ch03.xml: Add warning about restructuring your working
  copy without letting svn know.

* src/en/TODO: Remove task. 

Modified: trunk/src/en/TODO
--- trunk/src/en/TODO	(original)
+++ trunk/src/en/TODO	Mon May 16 09:54:21 2005
@@ -37,23 +37,6 @@
-To be fixed by fitz:
-   - explain the "magic rule" of working copy management: you must
-     always use 'svn' to manipulate files and dirs (cp, mv, add, rm,
-     etc.), *except* for editing.  Editing can be done without telling
-     svn; it notices this later on.  users are craving these two
-     simple sentences as an overview at the beginning of the chapter;
-     for someone who has never used CVS, it's apparently quite
-     confusing as to what sort of manipulations do and don't require
-     'svn'.
 To be fixed by cmpilato:
    - vendor branch section needs re-working.  again.  specifically,

Modified: trunk/src/en/book/ch03.xml
--- trunk/src/en/book/ch03.xml	(original)
+++ trunk/src/en/book/ch03.xml	Mon May 16 09:54:21 2005
@@ -624,6 +624,16 @@
         that you'll use most often to make tree changes (we'll cover
         <command>svn import</command> and <command>svn mkdir</command>
+      <warning>
+        <para>While you can edit your files with whatever tool you
+          like, you shouldn't change the structure of your working
+          copy without letting Subversion know what you're doing.  Use
+          the <command>svn copy</command>, <command>svn
+          delete</command>, and <command>svn move</command> commands
+          to change the structure of your working copy, and use the
+          <command>svn add</command> command to place new files and
+          directories under version control.</para> </warning>

More information about the svnbook-dev mailing list