|
Size: 1325
Comment:
|
← Revision 14 as of 2009-05-19 19:31:00 ⇥
Size: 137
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| This page will need to be moved to a more permanent place once this tutorial is completed. Please help me with a good name for the page! | |
| Line 9: | Line 8: |
| Outline: * Why the heck would I want to use mq? * How is mq a "stack"? (are there really 2 stacks?) * Tutorial on using mq: * Installing mq * Getting a repo to do work on (use hg for a sample!) * Initializing mq on that repo (make it versioned) * Creating and editing a patch * qnew seems to push the patch to the repo stack. * qrefresh refreshes the patch, not only in the patches folder, but also in the repo. * use qnew -m "message" to control the message that will be used when commiting this patch to the repo. * Creating another patch * Version my patches so far (qcommit) * Spliting the previous patch (edit patch to leave out 2nd patch and do something like: patch -p1 -R < p1b ; hg qrefresh; hg qnew -M "foo" p1b ; patch -p1 < p1b) * Propagating my patches (push all patches we wish to "publish", hg mail that) * Pointers to other docos: MqExtension, see the {{{hgext/mq-howto}}} file. |
|
| Line 26: | Line 9: |
| * Questions: * Why does qrefresh take out the {{{[mq]:}}} substring from the changeset message in the repo? |
Moved to MqTutorial |
