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

Re: question about checkout and commit

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-02-03 20:41:44 CET

bianyanghui@yeah.net wrote:

>The svn:externals is really a great features. It works well in my computer.
>I have just checked the svn status and svn commit. These
>two command doesn't examine the exteral items exactly as you pointed out.SVN status command even gives the annoying ?file for the external items. I would like to advise it to be included in the final release but it's up to you team.
>

i'd say check the issues database and if there isn't one filed about
that, file one. it's certainly something that should work.

>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.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 3 20:42:32 2003

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