Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: mdssirds.comp.pge.com: esp5 set sender to esp5@pge.com using -f Date: Mon, 13 Oct 2003 16:52:11 -0700 From: Edward Peschko To: Cygwin List Subject: Re: merging mingw and cygwin Message-ID: <20031013235211.GD26012@mdssirds.comp.pge.com> References: <1065936902.844.19.camel@localhost> <20031012062347.GA12677@mdssirds.comp.pge.com> <20031013190000.GB20245@mdssirds.comp.pge.com> <20031013203527.GA25036@mdssirds.comp.pge.com> <20031013213226.GC25036@mdssirds.comp.pge.com> <5.1.0.14.0.20031013193743.02ecc898@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20031013193743.02ecc898@127.0.0.1> User-Agent: Mutt/1.4.1i > The answer is - the Cygwin team is under no obligation to accept patches > to Cygwin to do anything. Patches are accepted and merged based on merit > of the patch and adherence with Cygwin standards. If your patch passes > these hurdles, it will be accepted. If not, it will be rejected (with > comments of course so you may very well be able to address the issues and > "resubmit"). No one will pre-approve a concept. We need to see code. > Fair enough, but you *can* 'pre' approve entrance to the developer's list. Remember, you try to subscribe and you get asked four questions? Well, I would like the venue to submit patches that way. Ed -- 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/