diff options
| author | Tomi Ollila <tomi.ollila@iki.fi> | 2011-09-01 10:25:29 +0300 |
|---|---|---|
| committer | Tomi Ollila <tomi.ollila@iki.fi> | 2011-09-01 10:25:29 +0300 |
| commit | ce3c99ec02d59aef553e28ff510bd1de9eaf1df3 (patch) | |
| tree | baeceb61aa90c81ab37c49834e2e38a2a20f82a0 | |
| parent | 4f967138b317bc77b0a87b7f02a801707397e9b2 (diff) | |
patchformatting.mdwn Send email section level tune.
| -rw-r--r-- | patchformatting.mdwn | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/patchformatting.mdwn b/patchformatting.mdwn index a61c41a..80de9ee 100644 --- a/patchformatting.mdwn +++ b/patchformatting.mdwn @@ -76,7 +76,11 @@ you can check with `git log` a 40-char commit-sha1 of the last commit every commit *after* that commit-sha1 will be used to generate patch files... -## Using git send-email to send patches. +## Sending patches + +### Using git send-email + +(This is the preferred way) If you try to execute `git send-email` and you'll get @@ -112,10 +116,10 @@ to your own email address to see how the messages appear in your mailbox. In this phase you can "streamline" your `git send-email` options for actual patch sending to the mailing list. -## Sending one patch using compatible (emacs) email client. +### Sending one patch using compatible (emacs) email client. One alternative way to send your patches is to use, for example, the -emacs mail client you've already used to send mails to notmuch mailing list. +emacs mail client you've already used to send mails to mailing list. In this case you have to be very careful to keep the patch contents unchanged: |