Mercurial > evolve

changeset 5194:f478ac0a818f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
readme: copywrite the section about branch policy, wrap long lines
author Anton Shestakov <av6@dwimlabs.net>
date Wed, 11 Mar 2020 15:55:36 +0700
parents a4d081923c81
children 85640f1feced
files README
diffstat 1 files changed, 9 insertions(+), 7 deletions(-) [+]
line wrap: on
line diff
--- 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: <CORE-NODE-ID>