Bookmarks with hg update question

[Scott Palmer]

On Mon, Jul 4, 2016 at 11:08 AM, Scott Palmer <swpalmer at gmail.com> wrote:

> On Fri, Jul 1, 2016 at 11:11 AM, Andrew Fischer <andrew at apastron.co>
> wrote:
>
>> On Thu, Jun 30, 2016 at 6:53 PM, Sietse Brouwer <sbbrouwer at gmail.com>
>> wrote:
>> > <snip>
>> >
>> > Workarounds bookmark users currently use
>> > ========================================
>> >
>> > James Reynolds asked: is there a setting that will prevent bookmarks
>> from
>> > moving when running `hg up`?
>> >
>> > Andrew Fischer's team used a bashrc setting that blocks bare `hg update`
>> >
>> > Mischa Becker used `hg up current~0` to update to a bookmark without
>> > activating it.
>> >
>> > David Demelier advised `hg pull -B the_bookmark_name` to put an
>> > inadvertently moved bookmark back in its old place.
>> > _______________________________________________
>>
>> Thanks Sietse for that summary of the thread so far. I actually missed
>> the last suggestion: 'hg pull -B the_bookmark_name' to restore a moved
>> bookmark, that's helpful to know!
>>
>> Great to see all of this discussion happening. I've been a mercurial
>> proponent for years, and the bookmark update is the only behaviour I
>> consistenly have trouble with when introducing it to other users.
>>
>
>
> I was just poking around in the Mercurial wiki and noticed this extension:
> https://www.mercurial-scm.org/wiki/JournalExtension
>
> I believe it is relevant to this conversation.  I have not tried it yet.
>
> It is scheduled to be integrated with core Mercurial in 3.9:
>
> https://www.mercurial-scm.org/wiki/ExperimentalExtensionsPlan?highlight=%28%5CbCategoryNewFeatures%5Cb%29
>
>
Also of note, the proposal of a "goto" command to eventually replace
"update":

https://www.mercurial-scm.org/wiki/GotoCommandPlan?highlight=%28%5CbCategoryNewFeatures%5Cb%29


Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20160704/850e41d7/attachment-0002.html>