Re: checking in a cvs working copy to subversion

Ryan Schmidt wrote:

> If the cvs update causes files in the working copy to be added, an
> svn add will not have been performed, and you'll have to run svn
> status to determine what files have been added, and manually svn add
> them before committing. If the cvs update causes files in the working
> copy to be deleted, an svn delete will not have been performed, and
> Subversion will complain that files it thought were under its control
> are no longer there, and getting out of that situation will likely be
> problematic.

"svn rm --force" should work just fine.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 18 03:29:22 2005