summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2018-02-21 18:23:52 +0100
committerWerner Koch <wk@gnupg.org>2018-02-21 18:27:23 +0100
commit70058cd9f944d620764e57c838209afae8a58c78 (patch)
tree28ed4654c87f6ce22991534d1d3467b214322ed1 /doc
parent887530733d0486ab68ff351c4855f5450c2d50e6 (diff)
downloadlibgpg-error-70058cd9f944d620764e57c838209afae8a58c78.tar.gz
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 <wk@gnupg.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/HACKING14
1 files changed, 10 insertions, 4 deletions
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 gnupg-devel@gnupg.org
+
+ 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 --to=gnupg-devel@gnupg.org --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 --to=gnupg-devel@gnupg.org --annotate --cover-letter -2
+ git send-email --annotate --cover-letter -2
(that prompts you for a summary mail to precede your actual
patch mails)