X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=utils%2Fperlbug.PL;h=9df77fe6825ab0fbb141092fb9769c3ac7ea5dd7;hb=114c60ecb1f775ef1deb4fdc8fb8e3a6f343d13d;hp=d0263f39aa7cfb0e1afa9eac073d31a5bc889b36;hpb=3bcc0c4bdd9457f6924030e81994a3583d07a8cb;p=p5sagit%2Fp5-mst-13.2.git diff --git a/utils/perlbug.PL b/utils/perlbug.PL index d0263f3..9df77fe 100644 --- a/utils/perlbug.PL +++ b/utils/perlbug.PL @@ -41,6 +41,8 @@ my @patches; while () { last if /^\s*}/; next if /^\s*#/; # preprocessor stuff + next if /PERL_GIT_UNPUSHED_COMMITS/; # XXX expand instead + next if /PERL_GIT_UNCOMMITTED_CHANGES/; # XXX expand instead chomp; s/^\s+,?\s*"?//; s/"?\s*,?$//; @@ -194,7 +196,11 @@ if ($outfile) { save_message_to_disk($outfile); } else { Send(); - print "\nThank you for taking the time to file a bug report!\n\n"; + if ($thanks) { + print "\nThank you for taking the time to send a thank-you message!\n\n"; + } else { + print "\nThank you for taking the time to file a bug report!\n\n"; + } } exit; @@ -600,6 +606,12 @@ for $entry on http://rt.cpan.org, and report your issue there. EOF $entry = ''; + } elsif (my $bug_tracker = $Module::CoreList::bug_tracker{$entry}) { + paraprint <<"EOF"; +$entry included with core Perl is copied directly from the CPAN distribution. +Please report bugs in $entry directly to its maintainers using $bug_tracker +EOF + $entry = ''; } elsif ($entry) { $category ||= 'library'; $report_about_module = $entry; @@ -1212,11 +1224,13 @@ B S<[ B<-v> ]> S<[ B<-a> I

]> S<[ B<-s> I ]> S<[ B<-b> I | B<-f> I ]> S<[ B<-F> I ]> S<[ B<-r> I ]> S<[ B<-e> I ]> S<[ B<-c> I | B<-C> ]> -S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> +S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> S<[ B<-T> ]> B S<[ B<-v> ]> S<[ B<-r> I ]> S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]> +B + =head1 DESCRIPTION @@ -1297,7 +1311,7 @@ L. =item Do you have a proper test case? The easier it is to reproduce your bug, the more likely it will be -fixed -- if nobody can duplicate your problem, it probably won't be +fixed -- if nobody can duplicate your problem, it probably won't be addressed. A good test case has most of these attributes: short, simple code; @@ -1367,6 +1381,12 @@ your Subject line informative. "a bug" is not informative. Neither is "perl crashes" nor is "HELP!!!". These don't help. A compact description of what's wrong is fine. +=item Can you use C to submit a thank-you note? + +Yes, you can do this by either using the C<-T> option, or by invoking +the program as C. Thank-you notes are good. It makes people +smile. + =back Having done your bit, please be prepared to wait, to be told the @@ -1486,6 +1506,10 @@ supply one on the command line. Test mode. The target address defaults to B. +=item B<-T> + +Send a thank-you note instead of a bug report. + =item B<-v> Include verbose configuration data in the report.