Mercurial > evolve
changeset 5421:f287f6b082f8
readme: improve wording in the contributing section
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Fri, 17 Jul 2020 09:50:27 +0800 |
| parents | 5a7a5de347b5 |
| children | 39cd95b6f566 |
| files | README.rst |
| diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/README.rst Fri Jul 17 09:43:37 2020 +0800 +++ b/README.rst Fri Jul 17 09:50:27 2020 +0800 @@ -126,9 +126,9 @@ .. _evolution: https://bz.mercurial-scm.org/buglist.cgi?component=evolution&query_format=advanced&resolution=--- -The recommended way is to create Merge Request on +The recommended way to submit a patch is to create a Merge Request on https://foss.heptapod.net/mercurial/evolve. To do so, create an account and -request access. You'll then be able to create topic based merge request. +request access. You'll then be able to create a topic-based merge request. Alternatively, you can use the patchbomb extension to send email to `mercurial devel <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>`_. @@ -161,8 +161,8 @@ Branch policy ------------- -The evolve tests 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 Mercurial. To deal with +this, we use named branches. There are two main branches: "stable" and "default". Tests on these branches are supposed to pass with the corresponding "default" and "stable" branch from