Mercurial > evolve
comparison README @ 4927:31cd40b1bb67
branching: merge with stable
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Fri, 15 Nov 2019 10:59:47 +0100 |
parents | dacbd20b2f72 |
children | 2392fe0e745a |
comparison
equal
deleted
inserted
replaced
4921:a7c01a2a3974 | 4927:31cd40b1bb67 |
---|---|
114 | 114 |
115 Bugs are to be reported on the mercurial's bug tracker (component: `evolution`_): | 115 Bugs are to be reported on the mercurial's bug tracker (component: `evolution`_): |
116 | 116 |
117 .. _evolution: https://bz.mercurial-scm.org/buglist.cgi?component=evolution&query_format=advanced&resolution=--- | 117 .. _evolution: https://bz.mercurial-scm.org/buglist.cgi?component=evolution&query_format=advanced&resolution=--- |
118 | 118 |
119 You can use the patchbomb extension to send email to `mercurial devel | 119 The recommended way is to create Merge Request on |
120 <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>`_. Please make | 120 https://dev.heptapod.net/mercurial/evolve. To do so, create an account and |
121 sure to use the evolve-ext flag when doing so. You can use a command like | 121 request access. You'll then be able to create topic based merge request. |
122 this:: | 122 |
123 Alternatively, you can use the patchbomb extension to send email to `mercurial | |
124 devel <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>`_. | |
125 Please make sure to use the evolve-ext flag when doing so. You can use a | |
126 command like this:: | |
123 | 127 |
124 $ hg email --to mercurial-devel@mercurial-scm.org --flag evolve-ext --rev '<your patches>' | 128 $ hg email --to mercurial-devel@mercurial-scm.org --flag evolve-ext --rev '<your patches>' |
125 | 129 |
126 Some of development happens on a public bitbucket repository (`evolve-devel`_) using the topic extension. | |
127 | |
128 .. _`evolve-devel`: https://bitbucket.org/octobus/evolve-devel | |
129 | 130 |
130 For guidelines on the patch description, see the `official Mercurial guideline`_. | 131 For guidelines on the patch description, see the `official Mercurial guideline`_. |
131 | 132 |
132 .. _`official Mercurial guideline`: https://mercurial-scm.org/wiki/ContributingChanges#Patch_descriptions | 133 .. _`official Mercurial guideline`: https://mercurial-scm.org/wiki/ContributingChanges#Patch_descriptions |
133 | 134 |