code review 10456044: codereview: force hg update after hg pull -u during hg sync

codereview: force hg update after hg pull -u during hg sync

If you hg update your client to an earlier CL, then
hg sync will move you back to tip if it pulls anything in,
but it will leave you where you are if it doesn't pull anything in.
That's confusing: make hg sync always update to tip.

[rsc, 2013-06-21 19:05:25]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go/

[bradfitz, 2013-06-21 20:21:45]

LGTM

[r, 2013-06-21 21:21:14]

AHA!

[dsymonds, 2013-06-22 04:07:10]

LGTM++

[rsc, 2013-06-24 18:17:19]

I changed this slightly, to use hg incoming to decide whether to do hg pull
-u or hg update. It's a mistake to do both, because if hg pull -u has
resolve conflicts, hg update will mark them as resolved, so that hg resolve
-l lists nothing, which makes it hard to find the files with <<< >>>
markers. If it seems okay for the day, I will submit tomorrow.

[rsc, 2013-06-25 21:23:27]

*** Submitted as https://code.google.com/p/go/source/detail?r=45419f700ae9 ***

codereview: force hg update after hg pull -u during hg sync

If you hg update your client to an earlier CL, then
hg sync will move you back to tip if it pulls anything in,
but it will leave you where you are if it doesn't pull anything in.
That's confusing: make hg sync always update to tip.

R=golang-dev, bradfitz, r, dsymonds
CC=golang-dev
https://codereview.appspot.com/10456044