On Thu, Oct 27, 2011 at 09:53:11AM +0000, Markus Schaber wrote:
> Hi,
>
> > Von: Attila Nagy [mailto:bra_at_fsn.hu]
> > BTW, with the current (1.7) WC-implementation, what possible problems do you see where this would be needed?
> > Previously with the per-directory .svn directories it was of course much easier, I could checkout the WC and move the .svn directory to its original place.
> > Now I (would) have to do this for all directories...
>
> If you have uncommitted property modifications, copies or moves in the working copy, a lossless transition (or repair) of the WC to 1.7 should be possible in the following ways:
>
You meant to say "*no* uncommitted property modifications, copies, or moves",
right?
But even then, in general, what you suggest isn't safe.
The broken working copy might be a mixed-revision working copy and
refer to pristine files from various revisions. In which case there
is no way a new checkout can replicate the needed DB state.
> 1) Preparation: Delete all .svn subdirectories in the working copy
>
> 2) create a separate checkout.
>
> 3) move or copy the .svn subdirectory of the new checkout into the top level directory of the existing working copy.
>
> Or:
>
> 1) Preparation: Delete all .svn subdirectories in the working copy
>
> 2) "svn checkout --force" in the existing working copy.
>
> I'm not sure whether this will work fine with externals, however. :-)
Received on 2011-10-27 12:07:55 CEST