On Tue, Oct 18, 2011 at 10:02 AM, Stefan Sperling <s...@elego.de> wrote:
>
>> But if i have a lot of different local modifications in sources, you propose
>> me to checkout??? You are crazy?
>
> Sorry, 'svn upgrade' cannot cope with corrupted 1.6 working copies.
> That is simply the way it is.
Someone in another thread mentioned doing fresh checkout, then copying
the 1.7 .svn directory over to the old workspace and then being able
to commit the outstanding changes. Is that a reasonable thing to try?
> If more people had tested the 1.7 pre-releases, your problem might
> have been caught before the 1.7.0 release. But it was not found.
I think there is a bigger question regarding why there are so many
corrupt 1.6 workspaces around that nothing so far had noticed. Should
people be concerned about that even if they aren't upgrading yet?
How can you tell if a workspace is corrupt?
--
Les Mikesell
lesmikes...@gmail.com
