Mercurial > evolve

comparison README @ 1147:94a710977768 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
readme: update the contribution process The inability to easily pull from pull request on bitbucket and the lack of obsolescence support there are too much pain. Patchbombed contribution are flowing so we drop the bitbucket mention in the README.
author Pierre-Yves David <pierre-yves.david@fb.com>
date Mon, 03 Nov 2014 10:24:35 +0000
parents ca17770d2ee9
children 458f883b68dc
comparison
equal deleted inserted replaced
1146:3de3d85069fd 1147:94a710977768
26 Or see the ``doc/`` directory for a local copy. 26 Or see the ``doc/`` directory for a local copy.
27 27
28 Contribute 28 Contribute
29 ========== 29 ==========
30 30
31 The simplest way to contribute is to issue a pull request on Bitbucket 31 Please use the patchbomb extension to send email to mercurial devel. Please
32 (https://bitbucket.org/marmoute/mutable-history). Alternatively, you 32 make sure to use the evolve-ext flag when doing so. You can use a command like
33 can use the patchbomb extension to send email to mercurial 33 this:
34 devel. Please make sure to use the evolve-ext flag when doing so. You
35 can use a command like this:
36 34
37 hg email --to mercurial-devel@selenic.com --flag evolve-ext --rev '<your patches>' 35 hg email --to mercurial-devel@selenic.com --flag evolve-ext --rev '<your patches>'
38 36
39 See also 37 See also
40 http://mercurial.selenic.com/wiki/ContributingChanges#Patch_descriptions 38 http://mercurial.selenic.com/wiki/ContributingChanges#Patch_descriptions