[PATCH libassuan v2] doc: clarify patch submission workflow

[Thorsten Behrens]

Signed-off-by: Thorsten Behrens <Thorsten.Behrens at CIB.de>
Co-authored-by: Todd Zullinger <tmz at pobox.com>
---
 doc/HACKING | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/doc/HACKING b/doc/HACKING
index 0e32f58..b67651e 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -108,3 +108,34 @@ grammar fixes."
   - That's it.  From now on you only need to add a "Signed-off-by:"
     line with your name and mail address to the commit message.  It is
     recommended to send the patches using a PGP/MIME signed mail.
+
+** Sending patches
+
+   - submitting patches, and subsequent discussions around them,
+     happens via the gnupg-devel at gnupg.org public mailing list
+
+   - send your patches to that list, preferably PGP/MIME signed. Make
+     sure to include a mention of 'libassuan' in the subject line,
+     the list is used for several different projects
+
+   - if you're working from the git repo, here's a suggested workflow:
+
+     - configure git send-email defaults:
+
+        git config format.subjectPrefix 'PATCH libassuan'
+        git config sendemail.to gnupg-devel at gnupg.org
+
+     - hack hack hack
+
+     - commit your changes; group changes into easily-reviewable commit
+       units, feel free to submit several patches at once
+
+     - e.g. if you want to submit a single patch on top of master, do:
+       git send-email --annotate -1
+
+     - e.g. if you have two commits on top of master, do:
+       git send-email --annotate --cover-letter -2
+       (that prompts you for a summary mail to precede your actual
+       patch mails)
+
+     - use --dry-run to test your setup
-- 
2.13.6