[PATCH RFC] update: default update should move as far forward as possible (issue3883)

[Durham Goode]

On 4/11/13 1:15 PM, "Matt Mackall" <mpm at selenic.com> wrote:

>First, I'm happy to agree that the old message sucks. But it does tell
>the user that a) they have an issue and b) it's somehow related to
>branching. 
>
>But "hg update" doing this:
>
> $ hg update
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
>
>says "everything's fine" to all but the most clueful, attentive users.

What about something like:

$ hg update
newer commits exist on a different branch - merge or rebase to reach them
0 files updated, 0 files merged, 0 files removed, 0 files unresolved


It's more explicit than the current message, it's relatively applicable to
both branch and bookmark flows, and hg update is still useful for moving
to descendants.