From: Arun Isaac <arunisaac@systemreboot.net>
To: 71481@debbugs.gnu.org
Cc: "Arun Isaac" <arunisaac@systemreboot.net>,
"Arun Isaac" <arunisaac@systemreboot.net>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>,
"Matthew Trzcinski" <matt@excalamus.com>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#71481] [PATCH 3/3] doc: Refer to mumi send-email in Submitting Patches.
Date: Mon, 10 Jun 2024 18:41:12 +0100 [thread overview]
Message-ID: <3309e26aa68fde18491caed27bf04cef42000bfc.1718025563.git.arunisaac@systemreboot.net> (raw)
In-Reply-To: <64b211c1bcab088e6502df4c824f91a28a6aa9e5.1718025563.git.arunisaac@systemreboot.net>
* doc/contributing.texi (Submitting Patches): Refer to mumi send-email.
Change-Id: I009cdc306220ef63e6641fac69d3453ab169bfa2
---
doc/contributing.texi | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index c089cfc95e..938c8bfdb1 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -2021,11 +2021,12 @@ Submitting Patches
@code{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.
+You may use your email client, the @command{git send-email} command
+(@pxref{Sending a Patch Series}) or the @command{mumi send-email}
+command (@pxref{Debbugs User Interfaces}). 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.
Expect some delay when you submit your very first patch to
@email{guix-patches@@gnu.org}. You have to wait until you get an
--
2.45.1
next prev parent reply other threads:[~2024-06-10 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 13:19 [bug#71481] [PATCH 1/3] doc: Document mumi am, compose and www subcommands Arun Isaac
2024-06-10 17:41 ` [bug#71481] [PATCH 2/3] doc: Add mumi CLI concept index entries Arun Isaac
2024-06-12 14:50 ` Maxim Cournoyer
2024-06-10 17:41 ` Arun Isaac [this message]
2024-06-12 14:53 ` [bug#71481] [PATCH 3/3] doc: Refer to mumi send-email in Submitting Patches Maxim Cournoyer
2024-06-12 14:52 ` [bug#71481] [PATCH 1/3] doc: Document mumi am, compose and www subcommands Maxim Cournoyer
2024-06-12 21:17 ` bug#71481: " Arun Isaac
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3309e26aa68fde18491caed27bf04cef42000bfc.1718025563.git.arunisaac@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=71481@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).