[PATCH 0 of 2 RFC] forward current bookmark on hg update

[Benoit Boissinot]

On Wed, Apr 20, 2011 at 5:04 PM, Matt Mackall <mpm at selenic.com> wrote:
> On Tue, 2011-04-19 at 15:34 +0300, Idan Kamara wrote:
>> 1. if you're currently updated to a bookmark and you try to 'hg update'
>> (e.g. after a pull), the bookmark won't move:
>>
>>   $ hg glog
>>   o  changeset:   1:e6a79fe2dd00
>>   |
>>   @  changeset:   0:bb12bb026c04
>>      bookmark:    foo
>>
>>   $ hg upd
>>   $ hg glog
>>   @  changeset:   1:e6a79fe2dd00
>>   |
>>   o  changeset:   0:bb12bb026c04
>>      bookmark:    foo
>>
>> this changes the behaviour to:
>>
>>   $ hg upd
>>   $ hg glog
>>   @  changeset:   1:e6a79fe2dd00
>>   |  bookmark:    foo
>>   |
>>   o  changeset:   0:bb12bb026c04
>>
>> 2. unbundle currently does this behind your back, I'm not sure why this was
>> decided but it felt unintuitive to me so I changed that too. instead you should
>> 'hg upd' after unbundling (as suggested by the output) to move the bookmark.
>
> David, could you look at these?

FYI, personally I prefer having bookmarks move on
pull/unbundle/commit. Idan why do you find it unintuitive?

cheers,

Benoit