Mercurial wipes repository history!?

Dirkjan Ochtman dirkjan at
Thu Apr 8 09:48:03 CDT 2010

On Thu, Apr 8, 2010 at 16:45, Jon Ribbens
<jon-mercurial at> wrote:
> Err, any circumstance in which the repository contains checked-in
> changes that are not stored elsewhere makes it obviously disastrous
> if that repository goes boom.

You either pulled them (they are stored elsewhere) or you committed
them, meaning you just rolled back a single commit (and the working
dir usually still contains the changes from that commit).

> Losing repositories is a far *worse* bug, if that's indeed what
> happened.

No, it's not, because we don't "lose" repositories unless they're fresh clones.

I suggest you read some docs on rollback or try different scenarios in
a test repository to get a feel for what it actually does, because it
doesn't look like you're getting it yet (even though Benoit and I have
explained it several times in this thread).



More information about the Mercurial mailing list