From 84cad487577c98362c0e1ea18600d4ea266a4cb4 Mon Sep 17 00:00:00 2001 From: Nicholas Clark Date: Mon, 27 Dec 2010 07:42:45 +0000 Subject: [PATCH] Fix links (and hence the podchecker test) after cce04bebd8af026c. --- pod/perlhack.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pod/perlhack.pod b/pod/perlhack.pod index c612684..ab82c30 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -279,7 +279,7 @@ backported to the maint branch. Only patches that survive the heat of the development branch get applied to maintenance versions. Your patch should update the documentation and test suite. See -L. If you have added or removed files in the distribution, +L. If you have added or removed files in the distribution, edit the MANIFEST file accordingly, sort the MANIFEST file using C, and include those changes as part of your patch. @@ -385,7 +385,7 @@ 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 Configure options as you can (e.g. MULTIPLICITY). If you have -profiling or memory tools, see L +profiling or memory tools, see L and L below for how to use them to further test your code. Remember that most of the people on P5P are doing this on their own time and don't have the time to debug your code. @@ -473,7 +473,7 @@ F. There are tests for nearly all the modules, built-ins and major bits of functionality. Test files all have a .t suffix. Module tests live in the F and F directories next to the module being -tested. Others live in F. See L +tested. Others live in F. See L =item Documentation -- 2.7.4