From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51412) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtx0u-0007kw-7y for guix-patches@gnu.org; Mon, 18 Sep 2017 10:27:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtx0o-000068-Df for guix-patches@gnu.org; Mon, 18 Sep 2017 10:27:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:37848) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dtx0o-00005y-9o for guix-patches@gnu.org; Mon, 18 Sep 2017 10:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dtx0o-0002nG-1f for guix-patches@gnu.org; Mon, 18 Sep 2017 10:27:02 -0400 Subject: [bug#28491] [PATCH] doc: Add "Sending a Patch Series" subsection. Resent-Message-ID: From: Jan Nieuwenhuizen References: <20170918092030.9691-1-janneke@gnu.org> <87h8w089a5.fsf@nicolasgoaziou.fr> Date: Mon, 18 Sep 2017 16:25:20 +0200 In-Reply-To: <87h8w089a5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 18 Sep 2017 14:45:54 +0200") Message-ID: <87377k3wz3.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Nicolas Goaziou Cc: 28491@debbugs.gnu.org --=-=-= Content-Type: text/plain Nicolas Goaziou writes: >> +the tracking number, @xref{Sending a Patch Series}. > > It should be @pxref. Thanks, changed both instances from @xref{} to (@pxref{..}), similar to other usage. Updated version attached Greetings, janneke --=-=-= Content-Type: text/x-patch; charset=utf-8 Content-Disposition: inline; filename=0001-doc-Add-Sending-a-Patch-Series-subsection.patch Content-Transfer-Encoding: quoted-printable >From 12b798f59e7d1397e1581f52a5321d5880cb33c1 Mon Sep 17 00:00:00 2001 From: Jan Nieuwenhuizen Date: Mon, 18 Sep 2017 11:12:43 +0200 Subject: [PATCH] doc: Add "Sending a Patch Series" subsection. MIME-Version: 1.0 Content-Type: text/plain; charset=3DUTF-8 Content-Transfer-Encoding: 8bit Searching for `git send-email' took you to the end of `Submitting Patches' section which said You may use your email client or the =E2=80=98git send-email=E2=80=99 co= mmand. 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..323b01628 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -298,11 +298,7 @@ This mailing list is backed by a Debbugs instance acce= ssible 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 @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. +the tracking number (@pxref{Sending a Patch Series}). =20 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 runn= ing the =20 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 (@pxref{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 +patches. + +@unnumberedsubsec Sending a Patch Series +@anchor{Sending a Patch Series} +@cindex patch series +@cindex @code{git send-email} +@cindex @code{git-send-email} + +When sending a patch series (e.g., using @code{git send-email}), 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. +@c Debbugs bug: https://debbugs.gnu.org/db/15/15361.html --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com --=-=-=--