build: Document how to use git send-email.

* autogen.rc: Add patches_to.
* autogen.sh: Run git config sendemail.to.
* doc/HACKING: Describe use of git send-email.
--

Co-authored-by: Todd Zullinger
Signed-off-by: Werner Koch <[email protected]>

3 files changed, 12 insertions, 4 deletions

diff --git a/autogen.rc b/autogen.rc
index a11c62f..4e1918a 100644
--- a/autogen.rc
+++ b/autogen.rc
@@ -1,6 +1,7 @@
 # autogen.sh configuration for libgpg-error                   -*- sh -*-
 
 display_name="Libgpg-error"
+patches_to="[email protected]"
 
 version_parts=2
 
diff --git a/autogen.sh b/autogen.sh
index b238550..4b511bf 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -469,6 +469,7 @@ EOF
       chmod +x  .git/hooks/commit-msg
       if [ x"${display_name}" != x ]; then
          git config format.subjectPrefix "PATCH ${display_name}"
+         git config sendemail.to "${patches_to}"
       fi
   fi
 fi
diff --git a/doc/HACKING b/doc/HACKING
index d379099..33b56d5 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -57,18 +57,24 @@
 
   - if you're working from the git repo, here's a suggested workflow:
 
+    - configure git send-email defaults:
+
+        git config format.subjectPrefix 'PATCH libgpg-error'
+        git config sendemail.to [email protected]
+
+      Note that running ./autogen.sh on a fresh clone will do this for
+      you.
+
     - 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 [email protected] --annotate -1
-      (please put a mention of libgpg-error into the subjects,
-      annotate lets you do that)
+      git send-email --annotate -1
 
     - e.g. if you have two commits on top of master, do:
-      git send-email [email protected] --annotate --cover-letter -2
+      git send-email --annotate --cover-letter -2
       (that prompts you for a summary mail to precede your actual
       patch mails)