Mercurial > evolve

comparison README @ 1603:6482497d859b stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
readme: point to mercurial-scm.org instead of selenic.com
author Pierre-Yves David <pierre-yves.david@fb.com>
date Thu, 04 Feb 2016 11:18:50 +0000
parents 7876ed4fceb7
children f69d8c25eeb7
comparison
equal deleted inserted replaced
1602:f932853783a5 1603:6482497d859b
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 Bugs are to be reported on the mercurial's bug tracker: http://bz.selenic.com/ 31 Bugs are to be reported on the mercurial's bug tracker: http://bz.mercurial-scm.com/
32 Use the the "evolution" component. 32 Use the the "evolution" component.
33 33
34 Please use the patchbomb extension to send email to mercurial devel. Please 34 Please use the patchbomb extension to send email to mercurial devel. Please
35 make sure to use the evolve-ext flag when doing so. You can use a command like 35 make sure to use the evolve-ext flag when doing so. You can use a command like
36 this: 36 this:
37 37
38 hg email --to mercurial-devel@selenic.com --flag evolve-ext --rev '<your patches>' 38 hg email --to mercurial-devel@mercurial-scm.org --flag evolve-ext --rev '<your patches>'
39 39
40 See also 40 See also
41 http://mercurial.selenic.com/wiki/ContributingChanges#Patch_descriptions 41 http://mercurial-scm.org/wiki/ContributingChanges#Patch_descriptions
42 for guidelines on the patch description. 42 for guidelines on the patch description.
43 43
44 Please don't forget to update and run the tests when you fix a bug or 44 Please don't forget to update and run the tests when you fix a bug or
45 add a feature. To run the tests, you need a working copy of Mercurial, 45 add a feature. To run the tests, you need a working copy of Mercurial,
46 say in $HGSRC: 46 say in $HGSRC: