me
/
guix
Archived
1
0
Fork 0
Code

doc: Refer to mumi send-email in Submitting Patches. 

* doc/contributing.texi (Submitting Patches): Refer to mumi send-email.

Change-Id: I009cdc306220ef63e6641fac69d3453ab169bfa2
master
Arun Isaac 2024-06-10 13:54:09 +01:00
parent d25bb39c51
commit f65bbca6e4
No known key found for this signature in database
GPG Key ID: 2E25EE8B61802BB3
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/contributing.texi
View File

@ -2021,11 +2021,12 @@ a subject, if your patch is to be applied on a branch other than
@code{master}, say @code{core-updates}, specify it in the subject like @code{master}, say @code{core-updates}, specify it in the subject like
@samp{[PATCH core-updates] @dots{}}. @samp{[PATCH core-updates] @dots{}}.
You may use your email client or the @command{git send-email} command You may use your email client, the @command{git send-email} command
(@pxref{Sending a Patch Series}). We prefer to get patches in plain (@pxref{Sending a Patch Series}) or the @command{mumi send-email}
text messages, either inline or as MIME attachments. You are advised to command (@pxref{Debbugs User Interfaces}). We prefer to get patches in
pay attention if your email client changes anything like line breaks or plain text messages, either inline or as MIME attachments. You are
indentation which could potentially break the patches. 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 Expect some delay when you submit your very first patch to
@email{guix-patches@@gnu.org}. You have to wait until you get an @email{guix-patches@@gnu.org}. You have to wait until you get an