Mark Miesfeld <[email protected]> wrote: > I closed that bug because the original submitter of the bug refused to > provide a test case that demonstrated the bug. So, I had to build my own > test case, and my test case worked fine.
There was nothing in the original report that suggested a problem with a MIME message, though. > I appreciate the work you do on bugs. I would like all bugs in ooRexx to > be fixed. I know if you open up a bug, you will have the courtesy to > follow up with it when needed. If we need more information, I know you > will provide it if we ask. > > So, please open up a new bug. ;-) Great. I posted here because you specifically said in your most recent update to that problem: ----------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2012-08-11 10:09 Message: Tested on both ooRexx 4.1.1 release and ooRexx trunk using ... ... I'm closing this as "Works for me" but it could also be "Out of date" If you would like to discuss this further, please discuss it on one of the ooRexx mailing lists, or even one of the project forums. ------------------------------------------------------------------------- And now you say that instead I need to raise a bunch of bug reports. How am I supposed to know when it is reasonable to /discuss/ issues and when it is reasonable to report bugs? -- Jeremy Nicoll - my opinions are my own ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
