Some way of preventing "hg update" without arguments?

[Andrew Fischer]

On Mon, Apr 4, 2016 at 2:15 AM, David Demelier <demelier.david at gmail.com>
wrote:

> Le 01/04/2016 17:42, Andrew Fischer a écrit :
>
>> We have a project with a workflow that uses bookmarks and multiple heads
>> on the default branch for small feature development. I've had to bring
>> several people up to speed who are not familiar with mercurial, and one
>> problem keeps eating up my time:
>>
>> They pull new code and simply call "hg update". Which of course updates
>> to tip and advances whatever bookmark they currently have active to that
>> tip. Just as expected. But then I get a message because their bookmark is
>> no longer on the local head they were working on and instead at tip. And
>> what to do, etc. etc. I always have to explain "don't just 'hg update'
>> after a pull. Look at what is new and update to the bookmark you want to
>> use".
>>
>>
> This bugs me as well, I have filed a bug [1] and if I have time this week
> I'll try to provide a patch to not move bookmarks on update with no
> arguments as I think it confuses lot of users and is rather not intuitive
> and non-sense.
>
> I also would like to see something like hg pull -u <revision> so that user
> can just do hg pull -u mybookmark just like hg clone -u has this kind of
> support.
>
> [1]: https://bz.mercurial-scm.org/show_bug.cgi?id=5172
>
>
That sounds like a feature we would make good use of; even if it was an
.hgrc option of some type. Thanks!

-- 
Andrew Fischer, PhD
Apastron, Co
903 1st ST N Hopkins, MN
952-373-1024
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20160405/41ca318f/attachment-0002.html>