[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/02: doc: Update patch submission instructions.

From: Ludovic Courtès
Subject: 01/02: doc: Update patch submission instructions.
Date: Mon, 13 Feb 2017 04:03:01 -0500 (EST)

civodul pushed a commit to branch master
in repository guix.

commit 230efa876fea3b38f78502bd759b2943651929de
Author: Ludovic Courtès <address@hidden>
Date:   Mon Feb 13 09:56:30 2017 +0100

    doc: Update patch submission instructions.
    * doc/contributing.texi (Submitting Patches): Add paragraph on
 doc/contributing.texi | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 4454df1..bbc9342 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -282,7 +282,19 @@ keyword parameters for procedures that take more than four 
 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{, mailing list}.
+format-patch} sent to the @email{} mailing list.
+This mailing list is backed by a Debbugs instance accessible at
address@hidden://}, 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}, where @var{NNN} is
+the tracking number.  When sending a patch series, please first send one
+message to @email{}, and then send subsequent
+patches to} to make sure they are kept
+together.  See @uref{, 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]