Re: Bug or feature?

On 9/1/07, Thomas Myers <tomlists@itainc.com> wrote:
> I had my complete project checked in. I then wanted to look at an
> earlier "build" So I did a update to a earlier revision. I probably
> should have checked out to another working directory, but I didn't.
>
> I then wanted to update to the latest revision. So I updated to head.
> When I did I got lots of errors because. 1) New directories that were
> added after the older revision I checked out. So check out to head
> would stop due to the directory already existing.
>
> Seems to me that the checkout should recognize that the folder is
> "valid" based on the .svn folder in it and allow the updating back to
> the head version.

When you did this, is it possible you had some local edits in files?
If you did, and these were in directories that Subversion wanted to
delete, then it would just unversion the directory (remove the .svn
folder) and leave the edited files behind. That would explain the
behavior.

The next version of Subversion adds a --force option to these commands
which causes it to tolerate the local files and just turn it into a
valid working copy.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org