diff options
| author | David Golden <dagolden@cpan.org> | 2011-06-20 15:52:55 -0400 |
|---|---|---|
| committer | David Golden <dagolden@cpan.org> | 2011-06-20 15:52:55 -0400 |
| commit | 7e5887a197ff102cf2829a635eb8a0b2457a0092 (patch) | |
| tree | 37641a4fe985bb11536d43cb1739168d05195389 /pod/perlhack.pod | |
| parent | 7bf422b50c78d6fbd98cdcfa712f3755582eea0a (diff) | |
| download | perl-7e5887a197ff102cf2829a635eb8a0b2457a0092.tar.gz | |
tweak perlhack and update known POD issues
Diffstat (limited to 'pod/perlhack.pod')
| -rw-r--r-- | pod/perlhack.pod | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod index ad4a117302..2d0fc1b68e 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -472,12 +472,12 @@ documentation or its listing on L<http://search.cpan.org/> for more information on reporting bugs and submitting patches. In most cases, patches to modules in F<cpan/> should be sent upstream -and should not be applied to the Perl core individually. If a patch to -a file in F<cpan/> absolutely cannot wait for the fix to be made -upstream, released to CPAN and copied to blead, you must add (or update) a -C<CUSTOMIZED> entry in the F<Porting/Maintainers.pl> file to flag that a -local modification has been made. See F<Porting/Maintainers.pl> for -more details. +and should not be applied to the Perl core individually. If a patch +to a file in F<cpan/> absolutely cannot wait for the fix to be made +upstream, released to CPAN and copied to blead, you must add (or +update) a C<CUSTOMIZED> entry in the F<"Porting/Maintainers.pl"> file +to flag that a local modification has been made. See +F<"Porting/Maintainers.pl"> for more details. In contrast, modules in the F<dist/> directory are maintained in the core. |