From: Brice Waegeneire <brice@waegenei.re>
To: 41191@debbugs.gnu.org
Subject: [bug#41191] [PATCH] doc: Specify the branch name in the title of a patch.
Date: Mon, 11 May 2020 20:42:54 +0200 [thread overview]
Message-ID: <20200511184254.21231-1-brice@waegenei.re> (raw)
* doc/contributing.texi (Submitting Patches): Add branch name in the
title of a patch if different than master.
---
doc/contributing.texi | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 9583120742..618d9008cc 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1083,12 +1083,14 @@ guix pull --url=/path/to/your/checkout --profile=/tmp/guix.master
@end enumerate
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 (@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.
+a subject, if your patch is to be applied on a branch other than master,
+say @code{core-updates}, specify it in the subject like @samp{[PATCH
+core-updates] @dots{}}. You may use your email client or the
+@command{git 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.
When a bug is resolved, please close the thread by sending an email to
@email{@var{NNN}-done@@debbugs.gnu.org}.
--
2.26.2
next reply other threads:[~2020-05-11 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 18:42 Brice Waegeneire [this message]
2020-05-11 19:43 ` [bug#41191] [PATCH] doc: Specify the branch name in the title of a patch Leo Famulari
2020-05-12 20:12 ` bug#41191: " Brice Waegeneire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200511184254.21231-1-brice@waegenei.re \
--to=brice@waegenei.re \
--cc=41191@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.