| [reply] |
| [reply] |
If you do "report" this to perlbug or the P5P, note me in as an advocate, even if I don't understand all of the details (I don't think I need to really).
I think and feel that it's a sane move, even if it requires higher-level discussions for 'approval'. I have a few cycles, and some hardware to play on if necessary.
| [reply] [d/l] |
Some tips for successfully submitting issues for Perl in case you haven't before:
1. Send an initial email without attachments to perlbug@perl.org describing the bug and including the word Perl so the spamfilter doesn't silently drop it. Send it from the perlbug program if you have email capability on your Perl development machine (I don't). Otherwise include perl -V output if it is relevant.
2. Log into rt.perl.org and hope that your account isn't randomly blocked from accessing all bug reports.
3. Go to your bug report and reply with attachments in the web interface.
| [reply] |