Re: [perl #24103] submissions.pod
leo -- appending myconfig to bug reports can't harm - never. Inspired by this bit of wisdom, (and my own earlier silliness with a useless backtrace), I've updated Aldo's patch faq to cover submissions to Parrot in general. I suggest it should go in docs. http://www.parrotcode.org/patchfaq can then be redirected there. You'll note I'm following the instructions for new files by submitting it to bugs-parrot without the [PATCH] prefix. Is this right? Should there be a [NEW] prefix as well? =item 7 Attach the patch and/or new file(s) that you're submitting. Double-check that you've done this, because it's really easy to forget. submissions.pod Description: application/applefile submissions.pod Description: application/text Mike
[perl #24103] submissions.pod
# New Ticket Created by Michael Scott # Please include the string: [perl #24103] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24103 leo -- appending myconfig to bug reports can't harm - never. Inspired by this bit of wisdom, (and my own earlier silliness with a useless backtrace), I've updated Aldo's patch faq to cover submissions to Parrot in general. I suggest it should go in docs. http://www.parrotcode.org/patchfaq can then be redirected there. You'll note I'm following the instructions for new files by submitting it to bugs-parrot without the [PATCH] prefix. Is this right? Should there be a [NEW] prefix as well? Mike
