[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[PATCH] More subcommands

From: Larry Shatzer <fugazi_at_zyx.net>
Date: 2003-02-25 17:17:56 CET

I decided to whip up a quick perl script to check for anymore stragglers. Below
is the result. I also decided to correct the ones in appa.xml, just in case.

Log message: Even more short to long subcommand conversion.

Index: doc/book/book/appa.xml
===================================================================
--- doc/book/book/appa.xml (revision 5089)
+++ doc/book/book/appa.xml (working copy)
@@ -73,8 +73,8 @@
         <listitem>
         <para>The <command>svn add</command> and <command>svn
           rm</command> commands work on directories now, just as they
- work on files. So do <command>svn cp</command> and
- <command>svn mv</command>. However, these commands do
+ work on files. So do <command>svn copy</command> and
+ <command>svn move</command>. However, these commands do
           <emphasis>not</emphasis> cause any kind of immediate change
           in the repository. Instead, the working items are simply
           <quote>scheduled</quote> for addition or deletion. No
@@ -184,7 +184,7 @@
     <para>The last subcommand in the list is new; it will not only
       remove local mods, but it will un-schedule operations such as
       adds and deletes. It's the preferred way to revert a file;
- running <command>rm file; svn up</command> will still work, but
+ running <command>rm file; svn update</command> will still work, but
       it blurs the purpose of updating. And, while we're on this
       subject&hellip;
 
@@ -432,7 +432,7 @@
 
     <para>Unlike CVS, a Subversion working copy is aware that it has
       checked out a module. That means that if somebody changes the
- definition of a module, then a call to <command>svn up</command>
+ definition of a module, then a call to <command>svn update</command>
       will update the working copy appropriately.</para>
 
     <para>Subversion defines modules as a list of directories within a
Index: doc/book/book/ch04.xml
===================================================================
--- doc/book/book/ch04.xml (revision 5089)
+++ doc/book/book/ch04.xml (working copy)
@@ -1009,7 +1009,7 @@
         your team. Remember that whatever you choose, it's not a
         permanent commitment. You can reorganize your repository at any
         time. Because branches and tags are ordinary directories, the
- <command>svn mv</command> command can move or rename them
+ <command>svn move</command> command can move or rename them
         however you wish. Switching from one layout to another is just
         a matter of issuing a series of server-side moves; if you don't
         like the way things are organized in the repository, just juggle
@@ -1030,7 +1030,7 @@
         anymore:</para>
 
 <screen>
-$ svn remove http://svn.example.com/repos/branches/calc/my-calc-branch \
+$ svn delete http://svn.example.com/repos/branches/calc/my-calc-branch \
              -m "Removing obsolete branch of calc project."
 
 Committed revision 375.
Index: doc/book/book/ch06.xml
===================================================================
--- doc/book/book/ch06.xml (revision 5089)
+++ doc/book/book/ch06.xml (working copy)
@@ -1740,7 +1740,7 @@
       the old <filename>main.c</filename> which Subversion knew about,
       and the new <filename>foobar.c</filename> which Subversion did
       not know about. You rename <filename>foobar.c</filename> to
- <filename>main.c</filename> and <command>svn mv</command> it
+ <filename>main.c</filename> and <command>svn move</command> it
       back to the new name. This way, Subversion will know that
       <filename>foobar.c</filename> is a descendant of
       <filename>main.c</filename>. <filename>dead.c</filename> has
@@ -1792,8 +1792,8 @@
         <para>Can be run at any point in time to bring an existing
           directory in the repository to exactly match an external
           directory. This script runs all the <command>svn
- add</command>, <command>svn rm</command> and optionally any
- <command>svn mv</command> commands as necessary.</para>
+ add</command>, <command>svn delete</command> and optionally any
+ <command>svn move</command> commands as necessary.</para>
       </listitem>
 
       <listitem>
Index: doc/book/book/ch08.xml
===================================================================
--- doc/book/book/ch08.xml (revision 5089)
+++ doc/book/book/ch08.xml (working copy)
@@ -428,7 +428,7 @@
             <title>Description</title>
             
             <para>Outputs the contents of the specified files or URLs.
- For listing the contents of directories, see svn ls.</para>
+ For listing the contents of directories, see svn list.</para>
           </refsect1>
 
           <refsect1>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 25 17:19:18 2003

This is an archived mail posted to the Subversion Dev mailing list.