[PATCH 1 of 2] remotenames: record bookmark changes in the journal

[Sean Farley]

Martijn Pieters <mj at zopatista.com> writes:

> On 1 July 2016 at 18:08, Sean Farley <sean at farley.io> wrote:
>> Martijn Pieters <mj at zopatista.com> writes:
>>
>>> # HG changeset patch
>>> # User Martijn Pieters <mjpieters at fb.com>
>>> # Date 1467374115 -3600
>>> #      Fri Jul 01 12:55:15 2016 +0100
>>> # Node ID 765689026f562a92b8eb58f4b4fad28cbbd4009b
>>> # Parent  183d5b47f7472b839a96e7be735bb7fbf8068969
>>> remotenames: record bookmark changes in the journal
>>>
>>> Any changed remote names are logged in the journal so users can track where the
>>> bookmark pointed to before.
>>
>> Why not store everything in the journal? Can't we just query it for all
>> remotenames and use that information to label / namespace things?
>
> Now that I have the right context, a second attempt at answering this. :-)
>
> I don't think an experimental extension is the place to replace the
> storage for all 3 of the current core namespaces: bookmarks, tags and
> branches. I see where this is going, and if the information that
> journal provides should be part of the core at some point, then yes, I
> agree that storing the information (who changed what name when) as
> part of the bookmark / tag / branch storage and exposing that via the
> namespace API is a great idea. But it is outside the scope and
> ambition for this extension for now. :-)

Ok, this is a good argument and I agree with your points. I've queued
this for testing (hopefully will use it tomorrow!)