distrib/utils/perlbug.PL

242     # Users address, used in message and in Reply-To header
248     # Subject of bug-report message
351 This program provides an easy way to create a message reporting a bug
364     # Prompt for subject of message, if needed
373 message. It should be a concise description of
739 the message to $address$andcc, display the message on
742 You may also save the message as a file to mail at another time.
751 		print "\n\nName of file to save message in [$file_save]: ";
773 		# Display the message
791 		# Send the message
792 		print "Are you certain you want to send this message?\n"
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
806 		# edit the message
833     # Message has been accepted for transmission -- Send the message
892 So you may attempt to find some way of sending your message, it has
934         quickly send a prepared message.
935   -F    File to output the resulting mail message to, instead of mailing.
940   -s    Subject to include with the message. You will be prompted
943         in a file with -f, you will get a chance to edit the message.
959   -h    Print this help message.
1058 Check in L<perldiag> to see what any Perl error message(s) mean.
1059 If message isn't in perldiag, it probably isn't generated by Perl.
1081 "Perl complained something" is not an exact error message.
1124 the message yourself, add the output produced by C<perlbug -d> and email
1158 perl maintainer actively watching perl porters for your message to
1164 in a file with B<-f>, you will get a chance to edit the message.
1188 prepared message.
1239 Subject to include with the message.  You will be prompted if you don't