Mercurial > evolve
changeset 2493:3ee8e9a12f41
doc: add documentation about effectflag experiment
| author | Boris Feld <boris.feld@octobus.net> |
|---|---|
| date | Mon, 29 May 2017 16:39:32 +0200 |
| parents | c9f1118b33d6 |
| children | 17bc96b54255 |
| files | README hgext3rd/evolve/__init__.py |
| diffstat | 2 files changed, 19 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/README Fri May 26 18:27:59 2017 +0200 +++ b/README Mon May 29 16:39:32 2017 +0200 @@ -117,6 +117,8 @@ - olog: add an 'obslog' alias - olog: add an '--all' option to show the whole obsolescence history tree. + - evolution: add an experiment to track the effect of rewrites. + (See hg help - evolve for details) - template: add a 'precursors' template that display the closests precursors of changesets - template: add a 'successors' template that display the closests successors of changesets - template: add a 'obsfate' template that display how a changeset has evolved
--- a/hgext3rd/evolve/__init__.py Fri May 26 18:27:59 2017 +0200 +++ b/hgext3rd/evolve/__init__.py Mon May 29 16:39:32 2017 +0200 @@ -77,6 +77,23 @@ [extensions] blackbox = + +Effect Flag Experiment +====================== + +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. + +The following config control the experiment:: + + [experimental] + # activate the registration of effect flags in obs markers + evolution.effect-flags = yes + +The effect flags are shown in the obglog command output without particular +configuration of you want to inspect them. """ evolutionhelptext = """