mq keeps its patches as an internal per-repo stack. This is much weaker than git's tree branches. Here's an example: let's say I've been working on a repo, and

mq keeps its patches as an internal per-repo stack. This is much weaker than git's tree branches. Here's an example: let's say I've been working on a repo, and have 2 current mq patches called A and B pushed. There's no way for me to pop A and B, then apply another patch called D in the current repo (at least as far as I could figure out). Also, even if there were, I'd have no way of then pushing A and B on top of D. The patches only work as a linear stack (D must come on top of B).