comment on

You don't need to sign up for bitcard etc. You just need to run the perlbug command-line client.

As for it's 'just one line'. What actually has to happen is that *someone* has to read the links you've provided, understand the issue, decide whether your patch is the best way to fix the issue (perhaps there are other considerations?), write an informative commit message, run the test suite, push the commit, and deal with any fallout if the smokes start failing. And field any queries from other p5pers, even though they aren't necessarily the one who understands the issue.

Whereas a bug report / RT ticket gets emailed to every one on the p5p mailing list, and the person who most understands the issue and/or the one with the spare time to apply the patch gets to deal with it. And all correspondence is logged against the ticket for future reference.

Dave.

In reply to Re^10: Perl 5 Optimizing Compiler, Part 4: LLVM Backend? by dave_the_m
in thread Perl 5 Optimizing Compiler, Part 4: LLVM Backend? by Will_the_Chill

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.


We don't bite newbies here... much
	PerlMonks