> 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.
Pretty average: http://mercurial.selenic.com/wiki/PruningDeadBranches > 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". I like mq as a power tool, but only for short-term work. Most of the time I don’t need it. Refreshing is painful to me whereas merging is straightforward. Mercurial devs themselves advocate real branches (named, pbranch or what-have-you) for long-term work. 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
