[PATCH 2 of 2] pull: new output message suggests better update action when a new branch head is added

[Kevin Berridge]

There are three different scenarios involving new branches:

1. no changes on your branch, new branch head added
2. changes on your branch but no new head, new branch head added
3. changes on your branch and new head, plus a new branch head added

If we want the message to favor information about your current branch maybe
there should be three messages like:

1: (No changes on this branch, but new branch heads added. Run 'hg branches'
to see branches)
2: (Changes on this branch, and new branch heads added. Run 'hg update' to
get latest working copy, 'hg branches' to see branches)
3: (New heads on this branch, and new branch heads added. Run 'hg heads' to
see heads, 'hg merge' to merge, 'hg branches' to see branches)

Thanks,
Kevin

On Tue, Mar 15, 2011 at 12:51 PM, Antoine Pitrou <solipsis at pitrou.net>wrote:

> On Tue, 15 Mar 2011 09:45:41 -0400
> Greg Ward <greg at gerg.ca> wrote:
> >
> > Speaking for myself, I generally don't care if new heads were added on
> > another branch.  I'm just interested in the *current* branch.
>
> Same experience here.
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20110315/8171379d/attachment.html>