Toggle diff (15 lines)diff --git a/HACKING b/HACKINGindex d1a26d2d6..f68753fee 100644--- a/HACKING+++ b/HACKING@@ -27,7 +27,7 @@ mailing list. When you get commit access, please make sure to follow the policy below (discussions of the policy can take place on email@example.com.) Non-trivial patches should always be posted to firstname.lastname@example.org (trivial-patches include fixing typos, etc.) This mailing list fills the+patches include fixing typos, etc.). This mailing list fills the patch-tracking database at [[https://bugs.gnu.org/guix-patches]]; see "Contributing" in the manual for details.-- 2.17.1
(name . Marius Bakke)(address . email@example.com)(address . firstname.lastname@example.org)
Bit confused with debbugs: I've closed the issue with`debbugs-gnu-send-control-message', passing "done" to it and using a smtpserver. Is it the correct way? Is "done" the right message (there are so many ofthem...). Does it matter which smtp server / e-mail I use? -- Pierre Neidhardt
(name . Pierre Neidhardt)(address . email@example.com)(address . firstname.lastname@example.org)
Pierre Neidhardt <email@example.com> writes:
Toggle quote (7 lines)> Bit confused with debbugs: I've closed the issue with> `debbugs-gnu-send-control-message', passing "done" to it and using a smtp> server.>> Is it the correct way? Is "done" the right message (there are so many of> them...). Does it matter which smtp server / e-mail I use?
Looks good to me: https://bugs.gnu.org/32244. Note: you can also simply CC <bugid-done>@debbugs.gnu.org to close itwith an email message. I did it now for clarity.