Rollback and pull problems
Kelly O'Hair
Kelly.Ohair at Sun.COM
Wed Dec 12 23:50:01 UTC 2007
In the OpenJDK we have talked about a changeset ID black list, never allowing
changesets on the black list to be pushed into a shared area.
For emergency use only of course, and we haven't implemented it yet that
I am aware of. It would create a bit of havoc to anyone that managed to
get a black listed changeset into their own repository, and had to undo it.
But it could prevent the shared area from ever getting it again.
Nasty problem.
-kto
Dustin Sallings wrote:
>
> On Dec 12, 2007, at 9:22, Martin Marques wrote:
>
>> So it's better to use backout. Right?
>
> That's a different tool, but it might be what you're looking for.
>
> backout makes a changeset that represents the opposite of another, so
> both exist. This is safely replicated and meaningful.
>
> rollback undoes a commit. You'd typically do that if you just committed
> something and realized you made a typo, or forgot to add a file or
> something. In this case, the first commit is no longer available.
>
> --
> Dustin Sallings
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
More information about the Mercurial
mailing list