Re: Unversioned files in working copies

Jan Evert van Grootheest wrote:
> The scenario, more or less, is this: there are at least two working
> copies involved here...
> WC1 and 2 are both up to date at some revision X.
> WC1 removes (or moves, which is a cp + rm!) a subdirectory and commits it.
> WC2 has changes in that removed directory. Now if WC2 tries to update
> you are in trouble. It can't (or won't) delete it, because there are
> changes in it. It can't update it, because it doesn't exist. It can't
> commit, because its gone.

This is a human communication issue more than it is a software issue. Directory
deletes and renames in a repository used by more than one person are a serious
issue and should be communicated via other channels than just the repository itself.

The way to unblock the commit is to move away the directory in WC2 that is
missing in the repository and let the remainder of the update proceed. Then
WC2's owner takes a stick and asks WC1's owner why a directory under active
development was deleted without warning. ;~)

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org