Re: Recurring problem with the SVN structure for WC

> PS: Is it so difficult to just change place of the .svn to be in a
> separated structure? I still have difficulty to see the "edge cases"
> like: <<what should happen if an update changes a directory to a file,
> yet the directory contains local changes?>> Can't it do the same
> procedure as today?

Well, at the least, you've introduced a new error state to deal with.
In the current model the content folder must exist if the
administration area exists (one is a file-system descendant of the
other). In the proposed approach this is not the case so you have to
either treat a missing content folder as missing content to be
recreated during an update, evidence of a remove, or a working copy
error.

To maintain the 'detachability' of the current approach you also need
to provide a 'detach' command to extract part of an existing working
copy into a new, self-contained, working copy.

My point is that it is not _just_ as simple as redirecting some paths.

--
Talden
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org