On Tue, Nov 06, 2012 at 10:20:07AM -0600, Jonathan Kotta wrote: > > PS: maybe you could rebase it on top of > > https://bitbucket.org/logilab/pylint/changeset/68ba9225985eb4f072b9b04abd9d8f71a37ee00a > > Done.
Thanks. > > to make the history look nicer. BTW, do you know about > > http://hg-lab.logilab.org/doc/mutable-history/html/ ? > > > > I've heard about it but never tried it. If I understand correctly, > with this I can safely remove the commit edfc3357659d, even though it > has been pushed? Mercurial 2.3 introduced http://mercurial.selenic.com/wiki/ChangesetEvolution that reads """ 6. State of the concept in version 2.4 Commit --amend, rebase and histedit can now create obsolescence marker instead of stripping. This behavior is disable by default. You need to explicitly enable Obsolescence support to get this behavior. """ Which means that rebasing your changeset will add an "obsolete" relation from the new cset to the old (edfc33...). You do not have to remove it: hg knows it is obsoleted and why. We use/develop that feature intensively at Logilab, but hopefully it will soon be enabled elsewhere and used when displaying repository history at bitbucket for example. Hope this helps spreading the word, -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
