At 04:08 PM 1/1/2005, you wrote:
>Brian Bruns wrote:
>>
>>
>>I think you really really really need to reevaluate what you say
>>before you hit send.
>>
>>The open source/free software developers that I communicate with/work
>>with wrote the stuff they did because they needed an
>>application/librar
Brian Bruns wrote:
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".
If you don't want to or are not able to pay attention to "real
world" bugs, cygw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sitting in Germany makes it difficult for me to physically send you a machine.
What I can do, though, is to virtually hand over the machine to you via the
net. I have an ADSL connection with 3 megabits/sec download and 512
kilobit/sec download
On Tue, Dec 28, 2004 at 05:29:10PM -0800, Brian Dessent wrote:
>Stephane Donze wrote:
>>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". If
>>y
Stephane Donze wrote:
> 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". If you
> don't want to or are not able to pay attention to "real world
On Tuesday, December 28, 2004 5:31 PM [EST], Stephane Donze wrote:
> Hi,
>
> Thank you for your reply. You are right, I did not look at the
> code, and I certainly do not pretend to be able to fix this problem.
>
> I am sorry to have to say that, but your message is a very good
> example of the fu
On Tue, Dec 28, 2004 at 11:31:00PM +0100, Stephane Donze wrote:
>I am sorry to have to say that, but your message is a very good example
>of the fundamental difference between a project that is useable and
>reliable, and a project that "almost works" and will never do more that
>that.
>
>[snip]
> 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 ran
> multiprocessor machines and nobody seems to care about it. You cannot
> just expect people to "wait until you someday have a system
> that shows
> the problem" everytime they encounter a bug.
Actually since Cygwin is a free project this is a reasonable
expectation. If you want this fixed send
Hi,
Thank you for your reply. You are right, I did not look at the code, and
I certainly do not pretend to be able to fix this problem.
I am sorry to have to say that, but your message is a very good example
of the fundamental difference between a project that is useable and
reliable, and a pro
On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote:
>we have encountered random hangs and crashes in cygwin (see output of
>cygcheck attached to this message) on a dual-processor server running
>Windows Server 2003. IMHO, the so-called "hyperthreading problems" reported
>recently on thi
11 matches
Mail list logo
