Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <3FAB0AB9.4080604@cwilson.fastmail.fm>
Date: Thu, 06 Nov 2003 22:00:09 -0500
From: Charles Wilson <cygwin@cwilson.fastmail.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@cygwin.com
Subject: Re: cygwin patches integrating back into standard gnu
References: <3FAABE0A.6090406@ekers.idps.co.uk> <1068154769.3faabf91a071f@www.nexusmail.uwaterloo.ca> <20031106222357.GA25195@redhat.com> <20031107023331.GA16244@mdssdev05.comp.pge.com> <3FAB099D.9090705@cwilson.fastmail.fm>
In-Reply-To: <3FAB099D.9090705@cwilson.fastmail.fm>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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/

