# HG changeset patch # User Anton Shestakov # Date 1583916936 -25200 # Node ID f478ac0a818fa9dc0288c1849a8eaaf1b50fcecc # Parent a4d081923c81971a4fe51287e8608b458eb31cca readme: copywrite the section about branch policy, wrap long lines diff -r a4d081923c81 -r f478ac0a818f README --- a/README Tue Mar 10 19:05:08 2020 +0700 +++ b/README Wed Mar 11 15:55:36 2020 +0700 @@ -142,17 +142,19 @@ Branch policy ------------- -The evolve test are highly impacted by changes in core. To deal with this, we use named branches. +The evolve tests are highly impacted by changes in core. To deal with this, we +use named branches. -There are two main branches: "stable" and "default". Tests on these branch are -supposed to pass with the corresponding "default" and "stable" branch from core -Mercurial. The documentation is built from the tip of stable. +There are two main branches: "stable" and "default". Tests on these branches +are supposed to pass with the corresponding "default" and "stable" branch from +core Mercurial. The documentation is built from the tip of stable. -In addition, we have compatibility branches to check tests on older version of +In addition, we have compatibility branches to check tests on older versions of Mercurial. They are the "mercurial-x.y" branches. They are used to apply -expected test change only, no code change should happen there. +expected test changes only, no code changes should happen there. -test output change from a changeset in core should adds the following line to their description: +Test output changes from a changeset in core should add the following line to +their patch description: CORE-TEST-OUTPUT-UPDATE: