Bast practice to use MQ with multiple computers?

[Peter Arrenbrecht]

On Mon, Feb 23, 2009 at 3:47 PM, Max (Weijun) Wang <Weijun.Wang at sun.com> wrote:
>> You could give pbranch a try.
>>  http://arrenbrecht.ch/mercurial/pbranch/
>
> Thanks for your suggestion. I'm reading the pbranch doc now. This extension
> uses multi-stage branches and store everything inside the main repo. On the
> other hand, mq stores everything in the .hg/patches directory, which is the
> only thing I need to maintain while doing the sync.
>
> In my case, it's not easy to directly access the office computer from home
> or the home computer from office, that's why I choose the Dropbox approach,
> and Dropbox works on file directories.

I see. With pbranch, you would have to explicitly exchange bundles via
the dropbox.

> BTW, pbranch can export to mq. Can it be created from an mq?

Not yet, alas. I'm meaning to add this.

>
> Thanks
> Max
>
> On Feb 23, 2009, at 9:44 PM, Peter Arrenbrecht wrote:
>
>> On Thu, Feb 19, 2009 at 4:23 AM, Weijun Wang <Weijun.Wang at sun.com> wrote:
>>>
>>> Hi All
>>>
>>> I work on a big repo both at home and at work. All my code changes are
>>> saved in MQ patches before they got pushed back into a public repo. So,
>>> in order to continuously working on both side, all I have to do is to
>>> synchronize the patches.
>>>
>>> So on the office computer I setup a Dropbox account and put (symlink)
>>> the .hg/patches directory into the Dropbox folder. Back at home, I
>>> symlink the same directory in the Dropbox into my .hg directory. Now
>>> everything looks file because I would have an identical patches
>>> directory across the 2 computers.
>>>
>>> The bad thing is about the status file now. Since the 2 computers may
>>> have different qpush/qpop actions, they should have different status.
>>> Now that the status file is the same, and I see error messages like
>>> "abort: popping would remove a revision not managed by this patch queue".
>>>
>>> How do you solve this problem? Unfortunately Dropbox have no .hgignore
>>> like features.
>>
>> You could give pbranch a try.
>>
>>  http://arrenbrecht.ch/mercurial/pbranch/
>>
>> -parren
>
>