me/guix
Archived
1
0
Fork 0
Code Activity

doc: Specify the branch name in the title of a patch.

Browse source 
* doc/contributing.texi (Submitting Patches): Add branch name in the
title of a patch if different than master.
This commit is contained in:
Brice Waegeneire 2020-05-03 12:11:49 +02:00
parent 62d18eb154
commit a1891cbffb
No known key found for this signature in database
GPG key ID: A94903A166A18FAE
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/contributing.texi
View file

@ -1083,12 +1083,14 @@ guix pull --url=/path/to/your/checkout --profile=/tmp/guix.master
@end enumerate @end enumerate
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as 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 a subject, if your patch is to be applied on a branch other than
send-email} command (@pxref{Sending a Patch Series}). We prefer to get @code{master}, say @code{core-updates}, specify it in the subject like
patches in plain text messages, either inline or as MIME attachments. @samp{[PATCH core-updates] @dots{}}. You may use your email client or
You are advised to pay attention if your email client changes anything the @command{git send-email} command (@pxref{Sending a Patch Series}).
like line breaks or indentation which could potentially break the We prefer to get patches in plain text messages, either inline or as
patches. 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 When a bug is resolved, please close the thread by sending an email to
@email{@var{NNN}-done@@debbugs.gnu.org}. @email{@var{NNN}-done@@debbugs.gnu.org}.