3.2 Calling Patcher

Now you want to build a patch with your changes, and prepare a message to submit them. The way Patcher works is currently to setup the message first, and then to control all subsequent operations from there. In other words, to create a patch, you actually ask Patcher to prepare a mail. Type this:

     M-x patcher-mail

First, you're prompted (with completion) for a project name (the first element of each project descriptor, remember?). We currently only have a “SuperProj” project, so hitting TAB will directly fill the minibuffer in with this only choice. Then, you're prompted for a subject line that will be used in the mail. Say something sensible here.

Three operations are now executed in turn:

1. Patcher prepares a mail buffer. The message will be sent to the address you specified with the :to-address project option, and the subject line now reads “[PATCH] something sensible here”.
2. Patcher now builds the patch. The command used to do this is specified in the Git theme, but it is a project option so it can be changed. Upon successful completion of this command (we assume that's indeed the case), the patch is inserted into the mail buffer. Some information about the patch is provided just above it (the command used, the files affected and so on).
3. Finally, Patcher generates ChangeLog skeletons from what it understands of the patch. This involves visiting the appropriate ChangeLog files, and creating initial entries.