DevelopersProcess » History » Version 1
Dan Smith, 12/24/2012 08:53 AM
| 1 | 1 | Dan Smith | h1. CHIRP Development Process |
|---|---|---|---|
| 2 | |||
| 3 | h2. Mercurial Configuration |
||
| 4 | |||
| 5 | Make sure that your mercurial tool is configured properly for CHIRP. This means having the correct username and email address specified, as well as the MQ extension enabled (for most cases). You can do this in your global mercurial configuration file, or in the one in the repository you're working on, which is @.hg/config@. You may also want to ensure that it has the patchbomb configuration enabled, which allows easy emailing out of mercurial itself. You probably want the following lines in your config file: |
||
| 6 | |||
| 7 | <pre> |
||
| 8 | [ui] |
||
| 9 | username = Joe Bob <joebob@gmail.com> |
||
| 10 | [extensions] |
||
| 11 | hgext.mq= |
||
| 12 | hgext.patchbomb= |
||
| 13 | [email] |
||
| 14 | from = Joe Bob <joebob@gmail.com> |
||
| 15 | method = smtp |
||
| 16 | |||
| 17 | [smtp] |
||
| 18 | host = smtp.gmail.com |
||
| 19 | </pre> |
||
| 20 | |||
| 21 | h2. Submitting a patch |
||
| 22 | |||
| 23 | Changes to CHIRP are welcome, but they should be in the correct format, and sent as a patch to the mailing list. The correct way to do this is to clone the upstream repository and |