> Mark> If we keep our strict requirement, then we're looking at one of two
> Mark> different approaches: live with the cycle, and automate it as much
> Mark> as possible to ease developer pain...
>
> That's what I want to see. As we were discussing on the phone just now,
> whereas now when a push is blocked we do:
>
> % hg pull
> % hg merge
> % hg commit
> % hg recommit
>
> we ought to be able to do
>
> % hg foo
>
> which would combine the above and allow for quicker turn-around. Meem (et
> al.): please pipe up if this would meet your needs or not.
That's an improvement in that it's less typing but still leaves one in a
potential cycle of:
hg push
[ blocked]
hg foo
hg push
[ blocked ]
hg foo
hg push
[ blocked ]
Why can't "hg push" do this for me?
--
meem
