You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "David A. Desrosiers" <de...@gnu-designs.com> on 2004/08/23 04:19:04 UTC
[BOOK PATCH] Clarification on 'cvs update' vs. 'svn status'
--- ch03.xml.orig 2004-08-23 00:12:17.000000000 -0400
+++ ch03.xml.new 2004-08-23 00:16:05.000000000 -0400
@@ -769,20 +769,30 @@
<sidebar>
<title>CVS Users: Hold That Update!</title>
- <para>You're probably used to using <command>cvs
- update</command> to see what changes you've made to your
- working copy. <command>svn status</command> will give you
- all the information you need regarding what has changed in
- your working copy—without accessing the repository
- or potentially incorporating new changes published by
- other users.</para>
+ <para>You're probably used to using <command>cvs update</command>
+ to see what changes have been made to the repository since the
+ last time you updated your working copy. This requires that cvs
+ contact the repository and diff the changes between what is in
+ the repository and your local working copy. It also brings
+ those updates down to your local working copy, bringing your
+ working copy into sync with the repository's version.</para>
+
+ <para>The command <command>svn status</command> will give you the
+ same sort of information that <command>cvs update</command>
+ does, regarding what has changed in your working copy
+ <emphasis>without</emphasis> accessing the repository or
+ potentially incorporating new changes published by other users
+ into your local working copy. It can provide similar
+ information, without changing your working copy at all.</para>
<para>In Subversion, <command>update</command> does just
that—it updates your working copy with any changes
- committed to the repository since the last time you've
- updated your working copy. You'll have to break the habit
- of using the <command>update</command> command to see what
- local modifications you've made.</para>
+ committed to the repository since the last time you've updated
+ your working copy, just like <command>cvs update</command>.
+ You'll have to break the habit of using the
+ <command>update</command> command to see what local
+ modifications you've made, if you don't want to change your
+ working copy.</para>
</sidebar>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [BOOK PATCH] Clarification on 'cvs update' vs. 'svn status'
Posted by "C. Michael Pilato" <cm...@collab.net>.
"David A. Desrosiers" <de...@gnu-designs.com> writes:
> + <para>You're probably used to using <command>cvs update</command>
> + to see what changes have been made to the repository since the
> + last time you updated your working copy. This requires that cvs
> + contact the repository and diff the changes between what is in
> + the repository and your local working copy. It also brings
> + those updates down to your local working copy, bringing your
> + working copy into sync with the repository's version.</para>
Eek! Your patch appears to eat up a column of indentation!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org