From 8310faf7732b7e4b26d2951de056b86df76eb113 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Sat, 11 Dec 2010 14:00:35 +0000 Subject: [PATCH] CG: use the "publish+mail comment" to inform -devel. --- Documentation/contributor/source-code.itexi | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi index ef8eec9b3e..80c78edbfe 100644 --- a/Documentation/contributor/source-code.itexi +++ b/Documentation/contributor/source-code.itexi @@ -1116,15 +1116,15 @@ can be used. @end itemize After prompting for your Google email address and password, the -patch set will be posted to Rietveld. +patch set will be posted to Rietveld, and you will be given a URL +for your patch. @subsubheading Announcing your patch set -You should then announce the patch by sending an email to -@code{lilypond-devel}, with a subject line starting with PATCH:, -asking for comments on the patch. Alternately, you may Publish + -Mail a (bogus) comment, in order to send an email to -lilypond-devel. +You should then announce the patch by logging into the code review +issue webpage and using @qq{Publish + Mail Comments} to add a +(mostly bogus) comment to your issue. The text of your comment +will be sent to our developer mailing list. @subsubheading Revisions -- 2.39.5