It's often necessary to test individual patches sent to a mailing list. Patches that are real attachments are trivial to download and merge. However, sometimes the patches are stored inline, in the message body, which makes thing slightly more difficult. If you're running Mozilla Thunderbird, you export emails containing inline emails as mbox file using *ImportExportTools* add-on. These can then be applied to a git repository using *git am <mbox-filename>*.
-
## Sending GitHub pull requests to the mailing list ==
+
## Sending GitHub pull requests to the mailing list
Getting a "git am"-compatible patch out of a GitHub pull requests is simple:
```
@@ 351,7 351,7 @@
Adjust the revision range as necessary if there are more than one patch.
-
## Poor-man's Symdiff ==
+
## Poor-man's Symdiff
Andj came up with a clever script in [http://thread.gmane.org/gmane.network.openvpn.devel/4869 an IRC meeting] to generate diffs that make reviewing refactoring patches easier:
