Bast practice to use MQ with multiple computers?

Martin Geisler mg at daimi.au.dk
Fri Feb 20 14:49:05 CST 2009


Max <weijun.wang at sun.com> writes:

> Marcin Kasperski <Marcin.Kasperski <at> mekk.waw.pl> writes:
>
>> I tried this approach some time ago and remember really ugly errors
>> happening if I failed to qpop all patches before sync-ing the main
>> repos. So this procedure is possible, but troublesome (in short you
>> should qpop -a on *both* sides, then sync both the main repo and the
>> patches repo)
>> 
>
> If I can remember to always gpop -a at both sides, there is no need to
> create a two-level repo.

You do not need to qpop on the remote side. When you synchronize the two
repositories in .hg/patches, the state of the remote patch queue is
irrelevant, in fact it is not even read. Here is nothing magical about
the two repositories, they just happen to reside in .hg/patches and
Mercurial does not care if they contain patches.

On the local side you will have to be careful about when updating the
.hg/patches repository. If you update .hg/patches to a revision which
deletes a patch which is currently applied, well then the mq extension
has a hard time figuring out what has happened... But again, there is
nothing magic going on here -- you could in principle just as well rsync
your .hg/patches directories back and forth.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090220/a6a1fe77/attachment.pgp 


More information about the Mercurial mailing list