D542: effectflag: document effect flag

[lothiraldan (Boris Feld)]

lothiraldan added a comment.


  @quark Thank you for reposting your comment here, it's helpful to not lose track 
  on all these discussions.
  
  We've had this experiment in Evolve for a little while now and the users using it
  are giving positive feedback. The next step is to upstream it in core but turned off by
  default like the others experiments and gather data and feedback.
  
  The effect-flag design poses indeed the limitation you're bringing up. I've updated the
  first commit message to make it more obvious:
  https://phab.mercurial-scm.org/D533
  
  However, I feel that it's not in this experiment scope, even though it 
  overlaps with effect-flag on content change tracking.
  
  I hope that with all our current experiments (operation, effect-flag) and
  potential future ones (content hash), we will be able to find the best
  way to store and display the obsolescence history, both for centralized
  and decentralized workflows, because we do have the same goal: making the
  obsolescence history understandable to users.
  
  I propose that we start a separate experiment, so users could use it
  separately from effect-flag. I would be happy to collaborate on a first
  version of this experiment before the sprint and use the sprint to further
  discuss the design, what do you think ?

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D542

To: lothiraldan, #hg-reviewers
Cc: quark, mercurial-devel