push: update to branch tip instead of tip We previously updated to the repository tip after pushing a revision, presumably on the assumption that tip would be the last revision we just pushed. This assumption is flawed for high traffic repositories. In particular, you previsouly would sometimes end up on a completley unrelated commit if someone else commits to a different branch in between the time we push a revision and pull it back from the server. This changes to instead update to the branch tip of the branch we were on at the beginning of the push. This should be either the revision we just pushed or a linear descendent of the revision we just pushed, with a fair degree of reliability.

97f2079e3778511944ffb6a662520580650a3993 1.0
09c016174e332eceda015d3f43d96d7e0228acf3 1.0.1
4359ddd73b009fbb356c52ea5d99cba25222ee7a 1.1
8e621dbb82d4363a85317638ad237e2817c56347 1.1.1
093ae2915b452539b44390ee4ea14987484e1eee 1.1.2
708234ad6c97fb52417e0b46a86c8373e25123a5 1.2
4bbc6bf947f56a92e95a04a27b94a9f72d5482d7 1.2.1
0cbf9fd89672e73165e1bb4db1ec8f7f65b95c94 1.3
07234759a3f750029ccaa001837d42fa12dd33ee 1.4
77b22e5b4ea6c248e079afd0f1e544cb5690ce20 1.5
d0f3a5c2cb56ce65d9ef1c611c8bfbebdc3bef34 1.5.1
7d47a0f731354505ed9ae8d60d2a6996e8c3294f 1.6
8caf1226adecb322e90ddb3817c604fa2fe8a66d 1.6.1
36f6d51b4edc31f1f9ce2d0d02965a85dd26a455 1.6.2
46523cdfd3b0cee0bf1366ab587686bb65211747 1.6.3