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

[Antoine Pitrou]

Hi,

> I have developed a branch-based alternative to MQ which I think is
> very useful for collaborative development and/or long-term maintenance
> of patches. Check out the extensive tutorial at:

Simply reading the tutorial and without actually trying it out:

- manually editing .hg/patchgraph sounds unwarranted for the simple cases.
Could there be a command "hg pinit patch-C" which does something like:
    "echo 'patch-C: <name of current branch>' >> .hg/patchgraph"
  followed by:
    "hg branch patch-C" 
(or the reverse)?

- the backport examples don't look convincing because they are much too
simplistic. I don't understand how "hg reapply" could help in a real-world
scenario with non-trivial patches.

- in "Deleting a patch", you say "We back out all the changes introduced by
patch-B". Shouldn't that read "We back out all the changes introduced by
patch-B1"?

- why isn't .hg/patchgraph committed in the repo? I see ".hg/patchgraph is a
file designed for editing by hand, comments and all". But it seems that in most
simple cases, people don't need to do hand editing if they are provided with a
few basic commands (e.g. "hg pinit" above).

- In "Merge Resolving Conflict", the output of "hg up p1" says "use hg pmerge"
but in the following command you use "hg merge" instead. This doesn't look
intuitive.

Regards

Antoine.