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: Wed, 27 Nov 2002 10:33:23 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: tty patch check in
Message-ID: <20021127153323.GA7333@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20021122233215 DOT A15763 AT fnord DOT io DOT com> <20021123062744 DOT GA12764 AT redhat DOT com> <20021123132755 DOT A16442 AT eris DOT io DOT com> <20021123200959 DOT GA9632 AT redhat DOT com> <20021123152714 DOT A20823 AT eris DOT io DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021123152714.A20823@eris.io.com>
User-Agent: Mutt/1.5.1i

On Sat, Nov 23, 2002 at 03:27:14PM -0600, Steve O wrote:
>On Sat, Nov 23, 2002 at 03:09:59PM -0500, Christopher Faylor wrote:
>> and so really had no bearing on the thread.  I made it clear that
>> increasing the buffer size was not a fix for everything.  I didn't need
>> to have it brought to my attention, YA.
>
>I apologize.  The way I read it, increasing the buffer size was going 
>to fix the paste problem, and case closed.  I clearly was reacting
>hastily. 
>
>> It needs more testing from more parties.  It would be nice if someone
>> like Egor could review the code, too.
>
>My understanding of the process was that changes would be committed
>to CVS then tested by the development community.  I think there's
>ample evidence that the patch doesn't cause immediate failure that
>would preclude developers from testing it.  If you really want
>more testing, checking it into CVS is the way to do it.

I was hoping that I wouldn't have to spend more time explaining this
but since I haven't seen any activity here, I guess that is not to
be.

I don't check in patches into cygwin unless I'm comfortable with them.
I've already said that I'd like to see more discussion and more testing.
That doesn't mean that I have to be involved making snapshots for
somebody or checking things in.  The theory is that this is a community
effort.  In practice that's only a little bit true.  I'm sorry that the
cygwin-developers community is so anemic that it can't support something
like this but I'm not going to let that lack cause possible cygwin
destabilization.

And, as far as my concerns about support are concerned, it seems like
there are some bug reports circulating about rxvt in the cygwin mailing
list that are not being addressed.  That fact makes me even more leery
about adding this patch.

I'm sorry but these are the facts of life for cygwin.

>>My problem with changes this major is that eventually next week, or
>>next year, Corinna and I will end up supporting it.
>
>True, so how can I make the code easier for you to support?  I can
>introduce fixes in small chunks, that eventually add up to what we have
>now.  Would that be better?

Fixes in small chunks are *always* better.  I didn't realize that was a
possibility for this patch.

cgf