Why Does Update with No Args Move Bookmark?

[Martin Geisler]

Benjamin Fritz <fritzophrenic at gmail.com> writes:

> Replying to list...whoops.
>
> On Fri, Oct 11, 2013 at 12:11 AM, Stephen Lee <sphen.lee at gmail.com> wrote:
>>>> The short answer is that it simplifies the common scenario where you
>>>> pull changes from some public server, and you have not made any
>>>> commits of your own. "hg up" moves you to the tip of the current
>>>> branch and drags the bookmark with it so you are ready to start
>>>> working.
>>>
>>> That scenario is actually not common in my experience.
>>
>> Not common then, but certainly possible.
>> Does anybody out there remember any other reason why update does this?
>
> I actually think for open-source projects that pulling from a public
> server, without having made any commits of your own, is probably the
> MOST common scenario.
>
> I don't know enough about using bookmarks to comment on whether this
> particular behavior of bookmarks simplifies that common scenario, or
> whether people who would be affected by this would even USE bookmarks,
> but the action of pulling without having made any changes should be
> very common.

Yes, if you follow an open source project, then you'll often pull+update
to stay current. However, that need not involve bookmarks which are
meant to be used for feature branches.

You could be following a feature branch in the project. The pull+update
would then do the right thing and forward the bookmark. I just don't see
this as the primary workflow for bookmarks.

-- 
Martin Geisler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20131012/76433f46/attachment.asc>