News for hackers. Stuff that matters.

A comment on Scaling Mercurial at Facebook. Parent comment

Re:Scaling Mercurial at Facebook by ahomescu1 on Tuesday January 07, 2014 @10:36PM (#7021514)
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).

[ Parent | on HN ]
Re:Scaling Mercurial at Facebook by rossjudson on Wednesday January 08, 2014 @10:04AM (#7023863)
I do this all the time. Pop B, pop A, reorder patch queue to put D first, push D, push A, push B. Check the docs.
[ Parent | on HN ]