effectflag: activate effect flag by default
Remove forcing effect-flag in test files
--- a/README Fri Jun 02 19:08:50 2017 +0200
+++ b/README Wed Jun 14 15:59:20 2017 +0200
@@ -124,6 +124,8 @@
6.3.2 - in progress
-------------------
+ - effect flag: the experiment is now active by default,
+ (see 'hg help -e evolve' to opt out)
- effect flag: fix a small bug related to hidden changeset,
- obshashrange: install a '.max-revs' option see extension help for details
--- a/hgext3rd/evolve/__init__.py Fri Jun 02 19:08:50 2017 +0200
+++ b/hgext3rd/evolve/__init__.py Wed Jun 14 15:59:20 2017 +0200
@@ -102,16 +102,16 @@
We are experimenting with a way to register what changed between a precursor
and its successors (content, description, parent, etc...). For example, having
this information is helpful to show what changed between an obsolete changeset
-and its tipmost successors.
+and its tipmost successors. This experiment is active by default
The following config control the experiment::
[experimental]
- # activate the registration of effect flags in obs markers
- evolution.effect-flags = yes
+ # deactivate the registration of effect flags in obs markers
+ evolution.effect-flags = false
The effect flags are shown in the obglog command output without particular
-configuration of you want to inspect them.
+configuration if you want to inspect them.
Templates
=========
--- a/hgext3rd/evolve/obshistory.py Fri Jun 02 19:08:50 2017 +0200
+++ b/hgext3rd/evolve/obshistory.py Wed Jun 14 15:59:20 2017 +0200
@@ -528,7 +528,7 @@
meaningful data. In the future, we can introduce way for commands to
provide precomputed effect to avoid the overhead.
"""
- if not repo.ui.configbool('experimental', 'evolution.effect-flags', False):
+ if not repo.ui.configbool('experimental', 'evolution.effect-flags', True):
return orig(repo, relations, flag, date, metadata, **kwargs)
if metadata is None:
metadata = {}