Mercurial wipes repository history!?

[Sune Foldager]

On 09-04-2010 11:28, Jon Ribbens wrote:
> On Thu, Apr 08, 2010 at 11:40:51AM -0500, Mark A. Flacy wrote:
>>     I'll add that if you really believe that someone would never want to
>>     rollback a clone, then they will not issue the command in the first
>>     place.
>
> That is obviously untrue - people can and will do it by mistake.
> When the commands are entered all in a row like my shell log at the
> start of this thread, then of course it's easy to see what's happening
> and nobody's likely to do that in real life. However if you have a
> repository that's been sitting there for days or weeks and you are
> mistaken as to what the last thing that happened to it is, then the
> repository suddenly going boom is fairly spectacularly suprising.

Yeah, so clone it again. It's not like there was any work in it that 
doesn't exist in another place.

> Version control systems are something you *need* confidence in,
> and I can tell you as a fact from personal experience that it suddenly
> denying all knowledge of everything you've ever done does *not*
> inspire confidence.

While we can all agree about that, I think it's time to put this "issue" 
to rest. If and when the original, real, problem can be reproduced, it 
will be looked at very seriously. This, on the other hand, is a 
pseudo-problem which we have now talked back and forth about for a long 
time.

The only time people are gonna lose anything by rolling back a fresh 
clone, is if they clone, instantly move to a country without internet 
and then rollback.

The original issue is interesting; this isn't.

/Sune