|
Size: 872
Comment:
|
Size: 1325
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| * 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. |
|
| Line 21: | Line 24: |
| * Pointers to other docos: MqExtension, see the {{{hgext/mq-howto}}} file. * Questions: * Why does qrefresh take out the {{{[mq]:}}} substring from the changeset message in the repo? |
Daniel Santa Cruz (byteshack)
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!
Mq Tutorial
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.
- Questions:
Why does qrefresh take out the [mq]: substring from the changeset message in the repo?