Project

General

Profile

Actions

DevelopersProcess » History » Revision 1

Revision 1/40 | Next »
Dan Smith, 12/24/2012 08:53 AM


h1. CHIRP Development Process

h2. Mercurial Configuration

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:

[ui]
username = Joe Bob 
[extensions]
hgext.mq=
hgext.patchbomb=
[email]
from = Joe Bob 
method = smtp

[smtp]
host = smtp.gmail.com

h2. Submitting a patch

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

Updated by Dan Smith almost 12 years ago · 1 revisions