[PATCH gpgme] doc: clarify patch submission workflow

[Thorsten Behrens]

Signed-off-by: Thorsten Behrens <Thorsten.Behrens at CIB.de>
---
 doc/HACKING | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/doc/HACKING b/doc/HACKING
index 83c0f517..3d3a2adf 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -89,6 +89,34 @@
     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 'gpgme' 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:
+
+     - 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 --to=gnupg-devel at gnupg.org --annotate -1
+       (please put a mention of gpgme into the subjects,
+       annotate lets you do that)
+
+     - e.g. if you have two commits on top of master, do:
+       git send-email --to=gnupg-devel at gnupg.org --annotate --cover-letter -2
+       (that prompts you for a summary mail to precede your actual
+       patch mails)
+
+     - use --dry-run to test your setup
+
 ** Coding standards
 
   Please follow the GNU coding standards.  If you are in doubt consult
-- 
2.13.6