Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 4 Nov 2000 23:24:59 -0500 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: test report on ver 1.1.5-4 Message-ID: <20001104232459.A17875@redhat.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <3A0436CD DOT B8B6B7D6 AT redhat DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001104134426 DOT 00c37450 AT pop DOT bresnanlink DOT net> <001901c046d2$b616adf0$5728fea9 AT timayum4srqln4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <001901c046d2$b616adf0$5728fea9@timayum4srqln4>; from tprince@computer.org on Sat, Nov 04, 2000 at 06:47:15PM -0800 On Sat, Nov 04, 2000 at 06:47:15PM -0800, Tim Prince wrote: >I do work on commercial projects which use MKS, yet I have cygwin running >on as many of the same boxes as it will run on, and prefer it for ad hoc >tasks like grepping, finding, editing and the freedom from worry about >violating the license. The changes I would like to make to cygwin generally >turn out to affect too many other things for them to go anywhere; I have an >FSF assignment on file just in case something does go through, although I >haven't dealt with the issues which may be raised by changing my employment. >I notified my new employer throught the internal process that I have FSF >assignments on file, covering prior work, but they are too busy for sure to >pay any attention to it. Unfortunately, FSF != Red Hat. Red Hat owns Cygwin. So any changes that you make to Cygwin require an Red Hat assignment. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com