Well, I apologize about that, I'm sorry, I may be a bit harsh, but you do realize that I fixed it on my box and that I supplied at least some solution/patch for all the problems (on Win32, on Un*x they wouldn't work). It needs someone with Un*x to correct them. As people with a free operating system haven't done it so far I installed Linux and I'm going to try to fix it so both platforms work myself. I tried some stuff already, but it needs some work. And I do have a life too :)
Don't bother fixing it unless you have a solution right away. You don't have to now that I'm so pissed that I've installed Linux and am trying to fix it myself. P.S. nmake is too stupid and GNU make is too intelligent. P.P.S. That was a week ago, I made a mistake. P.P.P.S Don't reply to this message unless you have something really important to say. Go do something useful. All I wanted was to know why there were no replies, I meant no harm and I didn't want to upset anyone. -Jaen Saul ----- Original Message ----- From: "Michael G Schwern" <[EMAIL PROTECTED]> To: "Jaen Saul" <[EMAIL PROTECTED]> Sent: Wednesday, December 12, 2001 3:33 PM Subject: Re: Hello? Win32 on fire? > On Wed, Dec 12, 2001 at 03:12:41PM +0200, Jaen Saul wrote: > > I sent a post about the brokenness of Parrot on Windows 5 days ago.... still > > no reaction... not one reply, positive or negative. Are you guys blind? > > This is not how you get work done in Free Software. It is, however, > an excellent way to piss off a few dozen overworked volunteer > programmers who do have lives, jobs and things to do over the course > of a week other than fix Parrot. > > If you wish for Win32 to be fixed posthaste, supply a patch with your > bug report. Otherwise you will have to simply wait with the > occasional polite reminder to the list that there's trouble. > > And an apology may well be in order. > > > -- > > Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ > Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One > Stupid am I? Stupid like a fox! >
