[issue14466] Rip out mq instructions

Francisco Martín Brugué added the comment: Just for the record: Thanks to the old mq workflow in the devguide I've learned about them and I'm now using it all the time to send and manage the patches. The only thing is that one should first use the “qqueue” functionality (see “hg help qqueue”

[issue14466] Rip out mq instructions

Antoine Pitrou added the comment: Done, thank you. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue14466] Rip out mq instructions

Roundup Robot added the comment: New changeset e1d4b6dc9702 by Antoine Pitrou in branch 'default': Issue #14466: remove mq-based workflow http://hg.python.org/devguide/rev/e1d4b6dc9702 -- nosy: +python-dev ___ Python tracker

[issue14466] Rip out mq instructions

Senthil Kumaran added the comment: On Tue, Apr 03, 2012 at 08:37:35AM +, Ezio Melotti wrote: > > Ezio Melotti added the comment: > > + hg import --no-commit < mywork.patch > > Is the '<' correct here? No!. It should just be hg import --no-commit mywork.patch. I asked around at PyCon

[issue14466] Rip out mq instructions

Ezio Melotti added the comment: + hg import --no-commit < mywork.patch Is the '<' correct here? I would also mention hg diff right away, and explain about adding/removing files after that. The rest looks good. -- ___ Python tracker

[issue14466] Rip out mq instructions

R. David Murray added the comment: LGTM. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue14466] Rip out mq instructions

Antoine Pitrou added the comment: Here is a patch. -- keywords: +patch Added file: http://bugs.python.org/file25102/ripmq.patch ___ Python tracker ___ __

[issue14466] Rip out mq instructions

Antoine Pitrou added the comment: > One person that I helped at the PyCon sprints was using it, because > the devguide said to. But I think she was more confused by it than > she would have been by 'hg diff', at least to start out. Or maybe > not...but I wasn't able to help her with the mq com

[issue14466] Rip out mq instructions

R. David Murray added the comment: One person that I helped at the PyCon sprints was using it, because the devguide said to. But I think she was more confused by it than she would have been by 'hg diff', at least to start out. Or maybe not...but I wasn't able to help her with the mq command

[issue14466] Rip out mq instructions

Antoine Pitrou added the comment: > No one uses it? I'm surprised. I do and it seems to me by far the > easiest and safest way to maintain patches in progress when there is > constant churn. Ah, good to know :) My wording was a bit too strong then. However, I rarely see mq-produced patches wh

[issue14466] Rip out mq instructions

Ezio Melotti added the comment: +1 Most of the time "hg diff > issue12345.diff" is all that it's needed to produce a patch, and whenever I point someone to the devguide they usually get confused because they think they have to use mq. FWIW I mostly use uncommitted changes, possibly on more cl

[issue14466] Rip out mq instructions

Ned Deily added the comment: No one uses it? I'm surprised. I do and it seems to me by far the easiest and safest way to maintain patches in progress when there is constant churn. -- nosy: +ned.deily ___ Python tracker

[issue14466] Rip out mq instructions

Antoine Pitrou added the comment: > I, for one, use both uncommitted-changes and named branches; the > former is easiest, but the latter safer: if I screw up a merge in a > clone where I use a named branch, I can revert and retry the merge, > but if I screw up merging pulled changes with my unco

[issue14466] Rip out mq instructions

Éric Araujo added the comment: Yes please. We already have text if we look at the history before 73e11f64a704; we only need to agree on recommending “uncommitted changes in a clone” (which is okay to share patches but not for not ideal for more than one person working on something), named br

[issue14466] Rip out mq instructions

Changes by Antoine Pitrou : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue14466] Rip out mq instructions

New submission from Antoine Pitrou : The devguide describes a mq-based approach (*) for generating patches, but it seems nobody (almost) uses it. We should therefore replace that description with a more traditional one ("hg diff"). (*) http://docs.python.org/devguide/patch.html#tool-usage ---