Le 22/03/2011 00:46, Greg Ewing a écrit : > Ben Finney wrote: >> That seems to me the ideal: preserve all revision history for those >> cases when some user will care about it, but *present* history cleanly >> by default. > > Seems to me the basic problem here is the way Mercurial > presents you with a big pile of changesets and not much > way of imposing any structure on them. > > There should be a hierarchy of changesets, so you can > look at the top level and get the big picture, while > being able to drill down into the details when you > need to.
That’s one way of saying “Mercurial should be Bazaar” <wink>. Bazaar apparently has a notion of mainline whereas Mercurial believes that all changesets are created equal. The tools are different. Regards _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
