--- Begin Message ---
|
Subject: |
[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 @address@hidden@@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 @address@hidden@@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, @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
the
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
+patches.
+
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{guix-patches@@gnu.org}, and then send
+subsequent patches to @address@hidden@@debbugs.gnu.org} to make sure
+they are kept together. See
address@hidden://debbugs.gnu.org/Advanced.html, the Debbugs documentation}
+for more information.
address@hidden Debbugs bug: https://debbugs.gnu.org/db/15/15361.html
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#28491] [PATCH] doc: Add "Sending a Patch Series" subsection. |
|
Date: |
Tue, 19 Sep 2017 17:26:51 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Ludovic Courtès writes:
>>> * doc/contributing.texi (Submitting Patches): Add a note about closing bug
>>> threads by mailing to address@hidden
>
> I’m fine with both patches, thank you!
Thanks, pushed to master as 4619b59cb49c5356eaea4650dee3d4de929e082a
> In the future, we should probably add a “Reviewing Patches” section as
> well. :-)
Yes...that should be easy to review ;-)
janneke
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
--- End Message ---