ANN: pbranch extension (alternative to mq, like topgit and bzr loom)

[Peter Arrenbrecht]

On Fri, Dec 12, 2008 at 6:43 PM, Leslie P. Polzer
<sky at viridian-project.de> wrote:
>
>> Ah, no. It's a graph of branches, each dedicated to one patch. And
>> each usually consisting of multiple changesets (tracing the evolution
>> of its patch). The graph defines the flow of automated merges between
>> the branches, and how the diffs between the branches, which define the
>> patches, are taken for submission upstream.
>
> I'd like to jump at the "automated merges" bit here.
>
> Would pbranch be suitable for collaborative topic branches that need
> to be rebased against one upstream branch regularly?

Hmm. pbranch does not rebase. It's about being non-destructive.

That said, I am planning an extension that allows me to record
dependencies that only affect automated merges, but not the diffs. The
main reason for this is to be able to maintain a patch graph against
multiple upstream versions. Like, for example, maintain an extension
against both hg-stable and hg-crew.

This, of course, can then be used to automate any desired merge flow
among branches.

I also want to add an `hg pincoming / poutgoing` command pair to list
csets that would get merged (akin to `hg --follow --rev target:null
--prune source`). And integrate them into pgraph like status, so `hg
pgraph --incoming`.

-parren