Mercurial wipes repository history!?
Jon Ribbens
jon-mercurial at unequivocal.co.uk
Thu Apr 8 09:54:28 CDT 2010
On Thu, Apr 08, 2010 at 04:45:39PM +0200, Benoit Boissinot wrote:
> A transaction is an operation modifying the history. As far as I can
> tell from your command log, the last transaction *is* the clone
> operation.
It is in that log, yes. It was not in the scenario we were trying to
replicate. It is also not at all clear to me that "clone" should be
a roll-backable operation (it is evidently not clear to the hg authors
either, since a local clone is not roll-backable and a remote clone
is.)
> > Surely it would be much better to make the remote behaviour fail too?
> > Suddenly vaporising the entire repository without warning is hardly
> > good behaviour to be more widely introduced!
>
> from hg help rollback:
>
> This command should be used with care. There is only one level of
> rollback, and there is no way to undo a rollback.
Sorry, is that supposed to have some relevance to the text quoted
above it?
More information about the Mercurial
mailing list