[PATCH 10 of 10] effectflag: detect when diff changed

[Kevin Bullock]

> On Jul 18, 2017, at 05:58, Boris Feld <boris.feld at octobus.net> wrote:
> 
> On Fri, 2017-07-14 at 13:48 -0400, Augie Fackler wrote:
>> On Fri, Jul 07, 2017 at 02:38:39PM +0200, Boris Feld wrote:
>>> # HG changeset patch
>>> # User Boris Feld <boris.feld at octobus.net>
>>> # Date 1499346007 -7200
>>> #      Thu Jul 06 15:00:07 2017 +0200
>>> # Node ID 449fc1c748c6e058e892a4c940e20137e52e7808
>>> # Parent  6a40d87dfedcce4064eb4bcdb131ed4d427fd4de
>>> # EXP-Topic effectflag
>>> effectflag: detect when diff changed
>> 
>> I've done some thinking about this, and I'd like to see a bit of a
>> unified story between these bits of metadata and
>> https://www.mercurial-scm.org/wiki/CommitCustodyConcept - I know
>> Mozilla is super-interested in that, and I think it's got a lot of
>> merit generally (instead of just recording how things mutate, we
>> could
>> also do things like have a CI system sign off on a revision in an
>> in-history way, for example).
> 
> CommitCustody seems somehow related to effect flag. While CommitCustody
> stores high-level information in a secure way (cryptography signed),
> effectflag store low-level information when a changeset evolve,
> basically what changes between a changeset and its successors.
> 
> Also I think CommitCustody will trigger a changeset evolution as I
> imagine it like this: I reviewed this patch, add my signature in meta
> (or somewhere else) and amend the changeset. Effectflag take place when
> a changeset evolution is triggered.
> 
> We should make them both collaborate or else each new custody will also
> store an effect flag.

Let's take this up again after the 4.3 release.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock