About mq use

hg user mercurialuser at gmail.com
Tue Nov 6 10:10:26 CST 2007


Following my previous question and after reading that mq is the
solution for a lot of problems, I decided to give it a try... but now
I'd like to clarify some points....

I did the following:

hg convert <from> <to>
cd <to>
hg qinit

hg qnew DefineBDOWN
<hack>
hg qrefresh
hg pop -a

hg qnew DotGrid
<hack>
hg qrefresh
hg pop -a

hg qnew ChangeObjectName
<hack>
hg qrefresh
hg pop -a

Command "hg qseries" reports
DefineBDOWN
DotGrid
ChangeObjectName

Pushing ONE patch a time I can work on a specific problem, then I may
push other patches to have a complete picture.
This is exactly what I wanted: to be able to work on single patches
without cloning the repository.

Since I didn't "hg qinit -c" I went to
cd .hg\patches
hg init

Now I want to copy this repository to a remote location. And I want to
propagate the mq patches in other repositories... what should I do
exactly ?
hg qcommit ? (but after a qcommit)
hg qclone from another repos ?

For this project I don't need to commit in the repository.

Sorry for my questions that may look stupid but I probably found the
"right" way to work with mercurial... if I can propagate mq patches
between repositories....

Thanks,
Francesco


More information about the Mercurial mailing list