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 Delivered-To: mailing list cygwin AT cygwin DOT com X-pair-Authenticated: 212.202.191.115 Reply-To: From: "Karsten Fleischer" To: Subject: RE: FW: ksh Date: Sun, 10 Feb 2002 04:29:01 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20020209182423.GM25500@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal > >>That source file is available for viewing at > >>http://www.research.att.com/sw/download/win32/omitted.c > >> > >>Chris, could you check that the disclaimer is OK? > > This file isn't intended for the Cygwin DLL so my opinion on this > doesn't really matter. My original patches were inside the Cygwin DLL, Glenn moved them outside. Now I'm intending to move some of them inside again. Is it OK given that special disclaimer? > Do you want to be the ksh maintainer for the cygwin distribution? Yes, I'd volunteer for this job. But... - the AT&T build system is quite different from the GNU standard autotools, so I' m not sure about how to post the sources. - I might become UWIN tainted in two months or so. My job seems to require obtaining a UWIN source code license. I must not contribute to Cygwin kernel code then, of course. But maintaining ksh for Cygwin can surely be cleared up with AT&T. In fact Cygwin is used at AT&T, too. I'm not tainted yet, just to assure you, I don't want to get into legal troubles also. Karsten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/