Backing out a misadventure.

[Stephen Rasku]

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.

...Stephen