Hi, On Wed, Feb 20, 2013 at 11:46:31PM -0500, Barry Warsaw wrote: > """ > 9. Git history is a bunch of lies > The primary output of development work should be source code. Is a > well-maintained history really such an important by-product? Most of the > arguments for rebase, in particular, rely on aesthetic judgments about “messy > merges” in the history, or “unreadable logs”. So rebase encourages you to lie > in order to provide other developers with a “clean”, “uncluttered” > history. Surely the correct solution is a better log output that can filter > out these unwanted merges. > """
http://mercurial.selenic.com/wiki/ChangesetEvolution """Changeset Evolution is a set of features to gracefully handle history rewriting operations. It offers a safe and simple way to refine changesets. Results of your local history rewriting operations can be propagated to other clones in a solid way. It is even possible for multiple people to rewrite the same part of the history in a distributed way.""" My humble opinion is that this is about to become a major feature of Mercurial. -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130222131741.ga20...@volans.logilab.fr