Backing out a misadventure.

[Smith, Michael]

<quote>
I made a number of changesets which I want to back out.  I backed out
the very first change I did and this gives me exactly what I want:
the repository exactly as it was before I started.  This creates a new
head.  This is not too much of a problem because we can just ignore
the spurious branch.  However, when I try and push back to the central
repository it complains about creating remote heads.  I can use "push
-f" to force it but I am wondering how this will affect other
developers after the pull from the central repository.

Will they be able to push their changes without this error message?
Will their changes be appended to the end of the newly backed out
change (which I want) or on the spurious branch (which I don't)?
Assume that none of the developers have yet pulled the spurious branch
at all.
</quote>

1. Push the new head to the server then tell the other users to start using the new head

or

2. Commit new changesets which reverse the changes you don't want. Possibly by reverting to the last good revision then committing it.



DISCLAIMER:---------------------------------------------------------------------------
This e-mail transmission and any documents, files and previous e-mail messages
attached to it are private and confidential. They may contain proprietary or copyright
material or information that is subject to legal professional privilege. They are for
the use of the intended recipient only.  Any unauthorised viewing, use, disclosure,
copying, alteration, storage or distribution of, or reliance on, this message is
strictly prohibited. No part may be reproduced, adapted or transmitted without the
written permission of the owner. If you have received this transmission in error, or
are not an authorised recipient, please immediately notify the sender by return email,
delete this message and all copies from your e-mail system, and destroy any printed
copies. Receipt by anyone other than the intended recipient should not be deemed a
waiver of any privilege or protection. Thales Australia does not warrant or represent
that this e-mail or any documents, files and previous e-mail messages attached are
error or virus free.
--------------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090610/910c76bd/attachment.htm