This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: "Hyperthreading" problems

> If you guys want cygwin to be used by real people, in real life 
> production or development environments, you should go a bit 
> further than 
> "I don't have the problem on my computer, so fix it yourself".

OK.  So, if he's unable to reproduce the problem, you want him
to... do what?  Make random changes to try and fix things?  How
is he supposed to know when he's fixed the problem if he can't
even manage to reproduce it in the first place?

> If you 
> don't want to or are not able to pay attention to "real world" bugs, 
> cygwin  will probably never be more than an "almost working" program 
> that runs on your computer the time to take nice screenshots, 
> but fails 
> miserably when users try to make it work in the real life.

I've been working for a company for three years now that relies
heavily on Cygwin as a foundation for commercial software.  Our
internal build system is capable of compiling various products
under either Cygwin or Linux, all from the same set of makefiles
and scripts.

We'd hardly be able to do any of that if Cygwin was an "almost
working" program not ready for use in "real life." It is not
without it's problems - you've pointed out one.  But overall,
Cygwin works, and it works well.

Why not get into the spirit of the season?  'Tis better to give
than to receive... PTC.

If you're unable to solve the problem yourself, then put a cash
value on your need to fix this bug, and hire someone to do it.
There are a lot of people that would *love* to pick up some
extra money around this time of year.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]