Lines Matching refs:report
52 # append a list of individual differences to the bug report.
114 # Also report selected environment variables.
125 # Changed in 1.24 Added '-F<file>' to save report HVDS 98-07-01
248 # Subject of bug-report message
254 # File to send as report
260 # Body of report
270 # Not OK - provide build failure template by finessing OK report
280 # OK - send "OK" report for build on this system
288 "perlbug -ok" and "perlbug -nok" do not report on Perl versions which
290 $date. If you really want to report this, use
447 A copy of this report can be sent to your local
469 Now you need to supply the bug report. Try to make
470 the report concise but descriptive. Include any
478 at the end of the report. If you are using any
483 the report. If "$ed" is the editor you want
508 # Generate scratch file to edit report in
511 # Prompt for file to read report from, if needed
515 What is the name of the file that contains your report?
539 # Generate report
540 open(REP,">$filename") or die "Unable to create report file `$filename': $!\n";
544 This is a $reptype report for perl from $from,
553 or die "Unable to read report file from `$file': $!\n";
562 [Please enter your report here]
571 close(REP) or die "Error closing report file: $!";
573 # read in the report template once so that
576 open(REP, "<$filename") or die "Unable to open report file `$filename': $!\n";
581 close(REP) or die "Error closing report file `$filename': $!";
656 # Edit the report
693 You may want to save your report to a file, so you can edit and mail it
700 # Check that we have a report that has some, eh, report in it.
715 I am sorry but it looks like you did not report anything.
738 Now that you have completed your report, would you like to send
767 close(REP) or die "Error closing report file `$filename': $!";
776 close(REP) or die "Error closing report file `$filename': $!";
869 (leaving bug report in $filename): $sts
890 report. We apologize for the inconvenience.
932 -v Include Verbose configuration data in the report
933 -f File containing the body of the report. Use this to
937 -a Address to send the report to. Defaults to `$address'.
938 -c Address to send copy of report to. Defaults to `$cc'.
942 -b Body of the report. If not included on the command line, or
954 -okay As -ok but allow report from old builds.
957 in the body of the report which you will be asked to edit.
958 -nokay As -nok but allow report from old builds.
1020 place to report bugs.
1027 compose your own report, and email it to B<perlbug@perl.org>. You might
1085 report. NOTE: unless your Perl has been compiled with debug info
1096 problem (to the extent you can) and report your discoveries.
1100 A bug report which I<includes a patch to fix it> will almost
1119 =item Can you use C<perlbug> to submit the report?
1121 B<perlbug> will, amongst other things, ensure your report includes
1123 to mail your report after you have typed it in, you may have to compose
1143 flames!). Feel free to resend your bug report if the next released
1152 Address to send the report to. Defaults to B<perlbug@perl.org>.
1163 Body of the report. If not included on the command line, or
1172 Address to send copy of report to. Defaults to the address of the
1187 File containing the body of the report. Use this to quickly send a
1206 with B<-v> to get more complete data. Only makes a report if this
1211 As B<-ok> except it will report on older systems.
1216 supplies a value for B<-s>, then requires you to edit the report
1217 and say what went wrong. Alternatively, a prepared report may be
1221 complete data. Only makes a report if this system is less than 60
1226 As B<-nok> except it will report on older systems.
1248 Include verbose configuration data in the report.
1271 None known (guess what must have been used to report them?)