Lines Matching refs:your
417 default shown is not your full internet e-mail address, please correct it.
423 your full internet e-mail address here.
447 A copy of this report can be sent to your local
476 Some information about your local
515 What is the name of the file that contains your report?
562 [Please enter your report here]
681 Did you mistype the name of your editor? If so, please
693 You may want to save your report to a file, so you can edit and mail it
738 Now that you have completed your report, would you like to send
800 That wasn't a clear "yes", so I won't send your message. If you are sure
801 your message should be sent, type in "yes" (without the quotes) at the
889 the perl package Mail::Send has not been installed, so I can't send your bug
892 So you may attempt to find some way of sending your message, it has
948 -d Data mode. This prints out your configuration data, without mailing
1027 compose your own report, and email it to B<perlbug@perl.org>. You might
1042 released version, get that one and see whether your bug has been
1045 You are on your own if you continue to use perl1 .. perl4.
1060 Consult your operating system documentation instead.
1070 The easier it is to reproduce your bug, the more likely it will be
1077 test suite. If you have the time, consider making your test case so
1085 report. NOTE: unless your Perl has been compiled with debug info
1088 their arguments. If possible, recompile your Perl with debug info and
1096 problem (to the extent you can) and report your discoveries.
1101 definitely be fixed. Use the C<diff> program to generate your patches
1107 detailed explanations about your fix.
1113 your changed file). Make sure you test your patch by applying it with
1115 same style as the code you are trying to patch. Make sure your patch
1121 B<perlbug> will, amongst other things, ensure your report includes
1122 crucial information about your version of perl. If C<perlbug> is unable
1123 to mail your report after you have typed it in, you may have to compose
1126 C<perlbug> at all on your system, be sure to include the entire output
1130 your Subject line informative. "a bug" not informative. Neither is
1136 Having done your bit, please be prepared to wait, to be told the bug
1137 is in your code, or even to get no reply at all. The Perl maintainers
1138 are busy folks, so if your problem is a small one or if it is difficult
1140 If it is important to you that your bug be fixed, do monitor the
1143 flames!). Feel free to resend your bug report if the next released
1144 version of perl comes out and your bug is still present.
1158 perl maintainer actively watching perl porters for your message to
1178 your configuration data, without mailing anything. You can use this