Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3FAB0AB9.4080604@cwilson.fastmail.fm>
Date:	Thu, 06 Nov 2003 22:00:09 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin patches integrating back into standard gnu
References:	<3FAABE0A DOT 6090406 AT ekers DOT idps DOT co DOT uk> <1068154769 DOT 3faabf91a071f AT www DOT nexusmail DOT uwaterloo DOT ca> <20031106222357 DOT GA25195 AT redhat DOT com> <20031107023331 DOT GA16244 AT mdssdev05 DOT comp DOT pge DOT com> <3FAB099D DOT 9090705 AT cwilson DOT fastmail DOT fm>
In-Reply-To:	<3FAB099D.9090705@cwilson.fastmail.fm>

Charles Wilson wrote:
> 
>   1) most (upstream) maintainers want small, easily digestible patches 
> -- so mega-patches must be split up into functional units.

See, for instance, this week's libtool-patches mailing list.
http://mail.gnu.org/archive/html/libtool-patches/2003-11/index.html

--
Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -