Les Mikesell wrote on Tue, Oct 18, 2011 at 10:18:24 -0500: > 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? (you mean "working copy")
Make a copy of it and upgrade that. Or, failing that, check all md5's in the working copy. But I expect the former option is far simpler for most people.
