summary refs log tree commit diff
path: root/doc/contributing.texi
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2017-02-13 09:56:30 +0100
committerLudovic Courtès <ludo@gnu.org>2017-02-13 10:02:54 +0100
commit230efa876fea3b38f78502bd759b2943651929de (patch)
tree1b4dd1e022f218568aa5f9f6140962740685cabd /doc/contributing.texi
parent43f10b5e7489b1f057987c1cd00fbb313e121d76 (diff)
downloadguix-230efa876fea3b38f78502bd759b2943651929de.tar.gz
doc: Update patch submission instructions.
* doc/contributing.texi (Submitting Patches): Add paragraph on
guix-patches@gnu.org.
Diffstat (limited to 'doc/contributing.texi')
-rw-r--r--doc/contributing.texi14
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 4454df1f98..bbc93424b4 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -282,7 +282,19 @@ keyword parameters for procedures that take more than four parameters.
 Development is done using the Git distributed version control system.
 Thus, access to the repository is not strictly necessary.  We welcome
 contributions in the form of patches as produced by @code{git
-format-patch} sent to the @email{guix-devel@@gnu.org, mailing list}.
+format-patch} sent to the @email{guix-patches@@gnu.org} mailing list.
+
+This mailing list is backed by a Debbugs instance accessible at
+@uref{https://bugs.gnu.org/guix-patches}, which allows us to keep track
+of submissions.  Each message sent to that mailing list gets a new
+tracking number assigned; people can then follow up on the submission by
+sending email to @code{@var{NNN}@@debbugs.gnu.org}, where @var{NNN} is
+the tracking number.  When sending a patch series, please first send one
+message to @email{guix-patches@@gnu.org}, and then send subsequent
+patches to @email{@var{NNN}@@debbugs.gnu.org} to make sure they are kept
+together.  See @uref{https://debbugs.gnu.org/Advanced.html, the Debbugs
+documentation}, for more information.
+
 Please write commit logs in the ChangeLog format (@pxref{Change Logs,,,
 standards, GNU Coding Standards}); you can check the commit history for
 examples.