From: Ævar Arnfjörð Bjarmason Date: Sun, 9 May 2010 12:38:29 +0000 (+0000) Subject: Clarify that mail to perlbug also goes to p5p X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=dce3ee48d7ab1ee0d37b9dd125e92b4c58a3ad8e;p=p5sagit%2Fp5-mst-13.2.git Clarify that mail to perlbug also goes to p5p The wording added in 64a8e22bd3 didn't clarify that mail to perlbug is also forwarded to perl5-porters. Make this section clearer so that it now explains that perlbug is just perl5-porters + RT tracking. See the discussion after Craig A. Berry's comment in RT #73914 for reference. --- diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index e7ef58a..7cf75e9 100644 --- a/pod/perlrepository.pod +++ b/pod/perlrepository.pod @@ -357,10 +357,13 @@ Now you should create a patch file for all your local changes: % git format-patch -M origin.. 0001-Rename-Leon-Brocard-to-Orange-Brocard.patch -You should now send an email to either perlbug@perl.org or -perl5-porters@perl.org with a description of your changes, and include -this patch file as an attachment. The perlbug address is preferred, -but use perl5-porters for patches intended for discussion. +You should now send an email to to +L with a description of your +changes, and include this patch file as an attachment. In addition to +being tracked by RT, mail to perlbug will automatically be forwarded +to perl5-porters. You should only send patches to +L directly if the +patch is not ready to be applied, but intended for discussion. See the next section for how to configure and use git to send these emails for you.