summaryrefslogtreecommitdiff
path: root/pod/perlgit.pod
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2013-07-02 13:13:44 -0700
committerFather Chrysostomos <sprout@cpan.org>2013-07-02 14:49:18 -0700
commit86032e6d69d00cea2f781c52c22e8d7418070b6a (patch)
tree19429b1fe4062e307d20b45f846f7a44f24901b8 /pod/perlgit.pod
parentbdb504800671ce2688cdfd83ea9009b88b2d5164 (diff)
downloadperl-86032e6d69d00cea2f781c52c22e8d7418070b6a.tar.gz
perlgit.pod: Remove one mention of p5p
We oughtn’t encourage people to send patches where they are likely to be lost.
Diffstat (limited to 'pod/perlgit.pod')
-rw-r--r--pod/perlgit.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perlgit.pod b/pod/perlgit.pod
index 8ae5112ade..2b00774d02 100644
--- a/pod/perlgit.pod
+++ b/pod/perlgit.pod
@@ -324,9 +324,9 @@ output.
=head2 Sending patch emails
-After you've generated your patch you should sent it to either
-perlbug@perl.org or perl5-porters@perl.org (as discussed L<in the
-previous section|/"Patch workflow"> with a normal mail client as an
+After you've generated your patch you should sent it
+to perlbug@perl.org (as discussed L<in the previous
+section|/"Patch workflow"> with a normal mail client as an
attachment, along with a description of the patch.
You B<must not> use git-send-email(1) to send patches generated with