"Pat Wenke" wrote
> I have configured VSS in the past, where your "working copy"
> for development can be the actual directory that is under
> source control.
VSS works a little differently in that when you import a directory into
the VSS database, that same directory automatically becomes your working
copy. In SVN it is a 2-stage process. You import a directory into the
SVN repository, but the directory you import is not made up into a
working copy - it does not have any of the .svn control directories. To
get a controlled WC you need to checkout from the repository, and the
checkout has to be into an empty folder. So it is a 2-stage process.
Maybe a bit wasteful on bandwidth, but you don't import very often -
usually when you have a major project which was not previously
controlled. Once you are using SVN, and you have a WC for your project,
you can just add files and folders from within your WC. In that case, it
behaves more like VSS and the new files are added to the repo and
version-controlled in your WC in one step.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 21 17:16:11 2004