r5222 - trunk/editor-manual/chapter03

jhuntwork at linuxfromscratch.org jhuntwork at linuxfromscratch.org
Sat May 7 17:05:19 PDT 2005


Author: jhuntwork
Date: 2005-05-07 18:05:19 -0600 (Sat, 07 May 2005)
New Revision: 5222

Modified:
   trunk/editor-manual/chapter03/moving.xml
Log:
Edits to chapter 3 moving

Modified: trunk/editor-manual/chapter03/moving.xml
===================================================================
--- trunk/editor-manual/chapter03/moving.xml	2005-05-07 23:58:52 UTC (rev 5221)
+++ trunk/editor-manual/chapter03/moving.xml	2005-05-08 00:05:19 UTC (rev 5222)
@@ -5,16 +5,16 @@
 ]>
 
 <sect1 id="ch03-moving">
-  <title>Moving files</title>
+  <title>svn move/mv/rename/ren</title>
   <?dbhtml filename="moving.html"?>
 
-  <para>Moving files: One of the (many) complaints against cvs is that it has no
-    concept of 1) moving files or 2) versioning directories.  If you need to
-    move a file, it's generally better to do it on the server manually. The
-    alternative is remove a file using <userinput>cvs delete</userinput> then
-    add the new version in the new place with <userinput>cvs add</userinput>.
-    The downside using this method is that you will lose the revision history
-    for that file. However, moving it on the server itself won't cause a loss of
-    revision history.
-  </para>
+  <para><userinput>svn move</userinput>, <userinput>svn mv</userinput>, 
+    <userinput>svn rename</userinput> or <userinput>svn ren</userinput>.
+    These commands move files from one location to another. One of the (many)
+    complaints against CVS was that it had no
+    concept of 1) moving files or 2) versioning directories.  If you needed to
+    move a file, it was generally better to do it on the server manually. With
+    Subversion, it's all a piece of cake. Note that the changes will only be
+    reflected on the Subversion server after you run the <userinput>svn commit</userinput>
+    command.</para>
 </sect1>




More information about the lfs-book mailing list