Antoine Pitrou writes: > Now, "hg strip" should definitely be absent of any recommended or even > suggested workflow. It's a power user tool for the experimented > developer/admin. Not the average hg command.
So what you're saying is that Mercurial by itself can't support the recommended workflow, because any "collapsing" of commits requires stripping, whether done by hg strip or implicitly by some other "non-average" hg command. > By the way, whether or not mq gets used is pretty much anyone's private > decision (unless we decide that patches must get split into logical > units and mailbombed for review ala mercurial-devel, which would be a > significant departure from our development habits). I don't see the connection; mq supplies "qfinish" for the purpose of turning a patch into a commit. All I'm suggesting is that "qrefresh" is a nicer way to handle both the collapsing process and the strip/ re-merge/recommit process, although there is the problem of reverting the commit back to an mq patch, which AFAIK requires a "strip --keep" followed by "qnew". _______________________________________________ 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
