Garrett Rooney <rooneg@electricjellyfish.net> writes:
> >When in CVS, update command returns the information of the modified
> >files but SVN doesn't. Actually such information is very
> >useful. Then I need to run SVN status. But SVN is slower than
> >CVS. It's more or less a waste of time to run two commands where
> >one command is enough. Doesn't SVN update actually do everything
> >SVN status does except printing the result to the console?
> >
>
> 'svn update' will tell you when something you've changed has been
> affected by the update (i.e. you change a file, then update and it's
> been changed in the repository, it will show you that a merge took
> place). if you just want to see what you've changed, use 'svn
> status', that's what it's there for. we're specifically trying to
> keep the two commands separate because determining what you've edited
> has nothing to do with updating your source.
Yes, read this:
http://svnbook.red-bean.com/book.html#svn-app-a-sect-3
In fact, you should probably read the whole Appendix, since it's all
about migrating from CVS to SVN.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 3 21:01:18 2003