diff options
| author | Dave Rolsky <autarch@urth.org> | 2009-10-30 11:11:51 -0500 |
|---|---|---|
| committer | Jesse Vincent <jesse@bestpractical.com> | 2009-10-30 12:44:51 -0400 |
| commit | 552d2b87467d02c0573847d29b6734bd06d733c6 (patch) | |
| tree | ea3342d592b6bed5973dbebd473d5d9fade6d420 | |
| parent | 168a53cc0d4ae0ff86a6afb90d36aee4047e7db2 (diff) | |
| download | perl-552d2b87467d02c0573847d29b6734bd06d733c6.tar.gz | |
Fix another reference to the now-gone patching.pod
| -rw-r--r-- | pod/perlhack.pod | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod index abd0933a87..6b96a33cc0 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -1710,9 +1710,8 @@ When you write your new code, please be conscious of existing code conventions used in the perl source files. See L<perlstyle> for details. Although most of the guidelines discussed seem to focus on Perl code, rather than c, they all apply (except when they don't ;). -See also I<Porting/patching.pod> file in the Perl source distribution -for lots of details about both formatting and submitting patches of -your changes. +Also see I<perlrepository> for lots of details about both formatting and +submitting patches of your changes. Lastly, TEST TEST TEST TEST TEST any code before posting to p5p. Test on as many platforms as you can find. Test as many perl |