RetroSearch Browse

Mon Mar 28 23:29:38 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-March/110203.html

On 3/28/2011 6:13 AM, Paul Moore wrote:

> This philosophy is essentially what the "mq" extension to Mercurial
> tries to capture. In mq, you maintain a series of patches "on top of"
> your repository, amending, refining and rebasing them as you wish
> until they are ready to commit, at which time you take them off the
> patch queue and convert them into final commits in the repository.

 From what you write, it seems that mq is actually an unordered patch 
set, not a queue (in the FIFO) sense. (Or do you have to commit and 
remove in FIFO order?) Why the confusing mislabel, if indeed I 
understood correctly?

-- 
Terry Jan Reedy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/110203.html below:

[Python-Dev] Hg: inter-branch workflow