If you have commit access to your project, you should read this. Otherwise, you may directly jump to Sending the Message.
Committing your changes involves three steps: preparing the commit command, preparing the commit log message, and actually committing the changes. Although Patcher can do all of this in one shot, it gives you control each step by default.
In order to start the commit process, simply type C-c C-p c
(patcher-mail-commit). Congratulations. You've just been
transported to a new buffer, the “log message” buffer. This buffer
lets you edit the log message that will accompany your commit. Note that
the message is initialized with the subject line of your mail. This is
also a project option.
Once you're satisfied with the log message, type C-c C-p c or
C-c C-c (patcher-logmsg-commit). This command computes the
commit command to use, and while you think that you're done this time,
you're not quite there yet. Indeed, patcher transports you to yet
another buffer called the “commit command” buffer. This buffer lets
you modify, or at least check the commit command to use.
The default commit command is specified in the Git theme, but it is of course a project option so it can be changed. Note that Patcher stores the log message in a temporary file and uses the -F option of the Git ‘commit’ command. Finally, note that Patcher has automatically appended the affected ChangeLog files to the commit command.
If the commit command suits you, type C-c C-p c or C-c C-c
(patcher-cmtcmd-commit). This time, you're done. If you had not
previously saved the ChangeLog files, Patcher will do it for you just
before committing.
As Patcher doesn't do pushing (neither pulling) yet, you may now want to push your changes to the remote repository by hand.