Using Mercurial patch queue repository on BitBucket for many users and patches

Question

Sorry for the many-part question, but I am having a difficult time understanding the intended methods to use a Mercurial Patch Queue with BitBucket, and Google isn\'t helpin

Answer 1

I think I found the answer to the second bullet on question #3:

1. Make sure the patch is in the applied queue in the source (local) repository.
2. Now I can select "Copy patch" from the "Export" context menu in TortoiseHg Workbench.
3. Then I can switch to the other local repository and select "Import..." from the "Repository" menu.
4. Click "Import from Clipboard"
5. In the drop-down list of the targets where the patch can be applied, select "patches".
6. Click Import

Now the patch from the other local repository appears (un-applied) in the local repository, and can easily be applied.

Unless I find answers to all my other questions myself, I likely won't be accepting this (my own) answer. I hope someone can help me with the other questions.

Answer 2

I'm afraid, with SF heap of clones you went by "far from ideal" path to the "unmanaged chaos" milestone

• Yon can use MQ-queues with Bitbucket (see mercurial-crew-mq repo or hgsubversion-layout-hacks repo) without additional repo, only with dir inside .hg for patches
• I can't see any reasons to storing patches in own repo (changesets are almost unreadable - diffs of diffs, history of patch have near-zero value)
• With patches in one repo you can provide easy exchange and update of patches
• qclone | push --mq provide bidirectional exchange of patches on top of vanilla code
• Group-work and P2P communication around some patches for contributors may be provided with MQCollab extension

Answer 3

Reviewing my old questions, I think my understanding of DVCS was too obscured by my familiarity with CVCS. In the end I simply allowed other SourceForge users to host their own clones of my repository and publish links to their repositories (see http://sourceforge.net/p/iotabuildit/wiki/reviews/).