On Thu, Oct 20, 2011 at 1:58 PM, Stefan Sperling <s...@elego.de> wrote:
>> > The unlucky user should simply get a new working copy.
>> > Working copies are and have always been considered disposable.
>>
>> So why bother to upgrade them at all if success is unimportant?
>
> You misunderstood what I meant.
No, I'm just being difficult because you didn't seem to care about the
potential for losing uncommitted changes.
> Most reports about failed upgrades so far were due to *corrupt* 1.6
> working copies. We cannot safely upgrade them, see Philip's reply.
>
> We do care about upgrading good 1.6 working copies, and have
> fixed several bugs in 1.7.1 based on the reports we received.
Is there any tool that you can run to do a corruption check on a 1.6
working copy that does not overwrite a needed 1.6 program and does not
actually do the upgrade? It seems like it would be a good thing to
know whether or not you were ready to upgrade.
--
Les Mikesell
lesmikes...@gmail.com
