Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 21 Nov 2002 22:14:33 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Cc: cygwin-developers AT cygwin DOT com
Subject: Re: Want to release 1.3.16
Message-ID: <20021122031433.GC5083@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>,
	cygwin-developers AT cygwin DOT com
References: <20021115220145 DOT GA27950 AT redhat DOT com> <Pine DOT GSO DOT 4 DOT 44 DOT 0211212151570 DOT 4275-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.44.0211212151570.4275-100000@slinky.cs.nyu.edu>
User-Agent: Mutt/1.5.1i

On Thu, Nov 21, 2002 at 09:59:21PM -0500, Igor Pechtchanski wrote:
>On Fri, 15 Nov 2002, Christopher Faylor wrote:
>>Should I wait for more ntsec stuff or is it ok to release 1.3.16?
>>There are a couple of problems I'd like to get resolved in a new
>>release.
>
>Steve Osborn's patch that solves the xterm/rxvt large paste deadlock
>didn't seem to make it into the CVS so far.  Could it please be applied
>before 1.3.16 is released?

I checked in an incredibly less obtrusive workaround for this recently.

The last communication that I saw on the subject was this:

>On Wed, 23 Oct 2002, Steve O wrote:
>> Though, I could of broke something.  If you want to persue this, you're
>> welcome to send me a test case off-list, and I'll see if anything unusual
>> is happening.
>
>I think the above quite adequately explained this.  If you think it's
>potentially fixable, let me know if you still want a test case.  And
>thanks again for the patch.

That led me to believe there was still more to do.

I was kind of hoping (even though I know it is fruitless) for more
feedback from the other people lurking in this list.

cgf