diff options
author | Karl Williamson <public@khwilliamson.com> | 2011-07-05 21:05:45 -0600 |
---|---|---|
committer | Karl Williamson <public@khwilliamson.com> | 2011-07-16 13:54:01 -0600 |
commit | 968d37620cb733823f5e3d114fce00e682460dd0 (patch) | |
tree | e1f5843dc603a2bfa3b0ff67462afe00cdde0f96 | |
parent | dff47061fe12fc16f86788ab67f56dfdd9f7475e (diff) | |
download | perl-968d37620cb733823f5e3d114fce00e682460dd0.tar.gz |
podcheck.t: Reword instructions slightly
This is to emphasize that things may be false positives, and
instead of jumping through hoops to shut it up, all you have
to do is --regen things.
-rw-r--r-- | t/porting/podcheck.t | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/t/porting/podcheck.t b/t/porting/podcheck.t index 4d7fe34fa0..873e810d87 100644 --- a/t/porting/podcheck.t +++ b/t/porting/podcheck.t @@ -1641,9 +1641,9 @@ if (%files_with_unknown_issues) { HOW TO GET THIS .t TO PASS There $were_count_files that had new potential problems identified. -Some of them may be real, and some of them may be because this program -isn't as smart as it likes to think it is. You can teach this program -to ignore the issues it has identified, and hence pass, by doing the +Some of them may be real, and some of them may be false positives, because +this program isn't as smart as it likes to think it is. You can teach this +program to ignore the issues it has identified, and hence pass, by doing the following: 1) If a problem is about a link to an unknown module or man page that @@ -1658,8 +1658,8 @@ following: ones you decided to, and rerun this test to verify that the fixes worked. -3) If there remain potential problems that you don't plan to fix right - now (or aren't really problems), +3) If there remain false positive or problems that you don't plan to fix right + now, $how_to That should cause all current potential problems to be accepted by the program, so that the next time it runs, they won't be flagged. |