Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 7 Jun 2004 10:31:57 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: The cygwin assignment (was [a subject which has been blacklisted, prematurely IMO]) Message-ID: <20040607143157.GA15068@coe.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040607041911 DOT GA10312 AT coe DOT casa DOT cgf DOT cx> <00b201c44c69$f86f0940$78d96f83 AT robinson DOT cam DOT ac DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00b201c44c69$f86f0940$78d96f83@robinson.cam.ac.uk> User-Agent: Mutt/1.4.1i On Mon, Jun 07, 2004 at 09:32:26AM +0100, Max Bowsher wrote: >*But* I'd be very interested to see the official response to Bas van >Gompel's questions, as they echo my own concerns about signing a Cygwin >assignment. And I think that information about barriers to >contributing to Cygwin is on topic. If you are having difficulty understanding Cygwin's assignment mechanism, you should take it up directly with Red Hat. No decision maker at Red Hat reads this mailing list. -- 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/