[Top][All Lists]

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

[bug#28491] [PATCH] doc: Add "Sending a Patch Series" subsection.

From: Jan Nieuwenhuizen
Subject: [bug#28491] [PATCH] doc: Add "Sending a Patch Series" subsection.
Date: Mon, 18 Sep 2017 11:20:30 +0200

Searching for `git send-email' took you to the end of `Submitting Patches'
section which said

   You may use your email client or the ‘git send-email’ command.

without further warning or remark.

* doc/contributing.texi (Sending a Patch Series): Move information about
debbugs bug 15361 to subsection.  Add git-send-email index entries.
(Submitting Patches): Reference it.
 doc/contributing.texi | 29 ++++++++++++++++++++---------
 1 file changed, 20 insertions(+), 9 deletions(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 00edd4771..71a465a37 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -298,11 +298,7 @@ This mailing list is backed by a Debbugs instance 
accessible at
 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.
+the tracking number, @xref{Sending a Patch Series}.
 Please write commit logs in the ChangeLog format (@pxref{Change Logs,,,
 standards, GNU Coding Standards}); you can check the commit history for
@@ -434,7 +430,22 @@ Please follow our code formatting rules, possibly running 
 When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
 a subject.  You may use your email client or the @command{git
-send-email} command.  We prefer to get patches in plain text messages,
-either inline or as MIME attachments.  You are advised to pay attention if
-your email client changes anything like line breaks or indentation which
-could potentially break the patches.
+send-email} command @xref{Sending a Patch Series}.  We prefer to get
+patches in plain text messages, either inline or as MIME attachments.
+You are advised to pay attention if your email client changes anything
+like line breaks or indentation which could potentially break the
address@hidden Sending a Patch Series
address@hidden a Patch Series}
address@hidden patch series
address@hidden @code{git send-email}
address@hidden @code{git-send-email}
+When sending a patch series (e.g., using @code{git send-email}), please
+first send one message to @email{}, and then send
+subsequent patches to} to make sure
+they are kept together.  See
address@hidden://, the Debbugs documentation}
+for more information.
address@hidden Debbugs bug:
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond
Freelance IT | Avatar®

reply via email to

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