On Thu, Aug 01, 2013 at 01:38:07PM +0400, Andrey Repin wrote:
>Greetings, starlight.2013z3!
>>Some people like myself cannot abide subscribing to firehose mailing
>>lists and prefer to view discussion threads with a browser. It does
>>not mean contributors, direct or indirect, are any of value. E
Greetings, starlight.201...@binnacle.cx!
> Some people like myself cannot abide subscribing
> to firehose mailing lists and prefer to view
> discussion threads with a browser. It does not
> mean contributors, direct or indirect, are any
> of value. Even if I were a direct contributor
> monitori
Fixes the CTRL-C problem and the point
behind it all, running a critical build
script, work as well.
>
>stephan($0.02);
>
>-Original Message-
>From: cygwin-owner at cygwin dot com
>On Behalf Of starlight.2013z3 at binnacle dot cx
>Sent: Wednesday, July 31, 2013 10:26 AM
>
Well I uncovered a serious regression
and expressed a willingness to track
down the cause.
However your nasty reply and bad attitude
assures that I will defintiely not help
now.
At 01:21 PM 7/31/2013 -0400, Christopher Faylor wrote:
>You are right in assuming that newer DLLs should
>work with old
On Wed, Jul 31, 2013 at 12:24:32PM -0400, starlight.201...@binnacle.cx wrote:
>Have been running 1.7.16 for some time and living with the annoying
>CTRL-C hang bug.
>
>Tried swapping in cygwin1.dll cyglsa.dll and cyglsa64.dll from 1.7.22-1
>without (thankfully) updating the entire CYGWIN release.
>
Hello,
Have been running 1.7.16 for some time
and living with the annoying CTRL-C hang
bug.
Tried swapping in cygwin1.dll cyglsa.dll
and cyglsa64.dll from 1.7.22-1 without
(thankfully) updating the entire CYGWIN
release.
The 22-1 DLLs fix the CTRL-C problem,
but cause a high-intensity parallel
b
6 matches
Mail list logo
