Why does hg pull changes my branch

[James Reynolds]

Do you use TortoiseHG?

On Wed, Jul 19, 2017 at 11:11 AM, Sébastien Pierre <
sebastien.pierre at gmail.com> wrote:

> Hi all,
>
> I've noticed that mercurial tends to change the current branch after an
> `hg pull`. Here's an example:
>
> [I] sebastien at Cerise ~/W/f/d/XXX>
>             *sebastien|4 ⑂ R567|567*
> hg pull
> pulling from ssh://hg@bitbucket.org/XXX/XXXX
> searching for changes
> adding changesets
> adding manifests
> adding file changes
> added 10 changesets with 10 changes to 5 files (+3 heads)
> (run 'hg heads .' to see heads, 'hg merge' to merge)
> 26 files updated, 0 files merged, 10 files removed, 0 files unresolved
>
> [I] sebastien at Cerise ~/W/f/d/XXX>
>                   *alex|5 ⑂ R568|577*
>
> The first line in bold shows we're on my branch at revision 567, the
> second line in bold shows we're on alex's branch at revision 568.
>
> I did not specify `hg pull -u`, and I don't have an alias to it either.
> I'm a bit puzzled by the fact that pulling changes branch, and revision as
> well for that matter.
>
> Any idea why this happens?
>
> Thanks!
>
> -- Sébastien
>
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20170719/dffa4ece/attachment-0002.html>