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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
