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

[Leslie P. Polzer]

> 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?

  Leslie

-- 
LinkedIn Profile: http://www.linkedin.com/in/polzer
Xing Profile: https://www.xing.com/profile/LeslieP_Polzer
Blog: http://blog.viridian-project.de/