It would help if you can be a little less vague in your descriptions. Are you moving the folder inside Versions? (You hadn't specified that.) If so, then yes, that's a feature that would be really nice to have. If you're moving in the Finder, having Versions installed (running or not) won't interfere with your copying behavior, and shouldn't.

On May 14, 2009, at 11:00 AM, Doug wrote:

Versions should do that for me.

On May 14, 10:16 am, Quinn Taylor <[email protected]> wrote:
It's probably because, by copying the folder, you've overwritten the
invisible .svn directory inside the old folder, and Subversion is
confused as to what it should do, since the working copy meta-
information can't be found.

Unfortunately, this is one of the fine points about Subversion that
can trip up those unfamiliar with version control. (Most other systems
have similar problems — distributed SCM tools such as git and
Mercurial are notable exceptions, but they also have a steeper
learning curve due to the more complex paradigm.)

The first correct solution is to only replace files inside
directories, or if you copy a directory in Finder, choose "Merge"
instead of "Replace". Remember that files are also versioned, so
you'll need to tell Subversion to get rid of files and/or directories
you no longer want.

The second correct solution is to delete the existing directory in
Subversion, then move the new directory in place and add it to
Subversion. Note that this will lose the history for the directory, so if you're just trying to change a few files or subdirectories, this is
not the best way to go.

Sorry the answers require more hands-on manipulation than one would
hope, but such is the price of the versioned safety net...

  - Quinn

On May 14, 2009, at 8:00 AM, Doug wrote:

When I copy a folder into a project, overwriting an existing folder,
Versions says it is "obstructed" and I can not perform any operations
on it.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to