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 Message-Id: <200201111554.g0BFsUd29617@dymwsm15.mailwatch.com> From: "Fleischer, Karsten (K.)" To: "'Corinna Vinschen'" Subject: RE: ksh on cygwin Date: Fri, 11 Jan 2002 10:53:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.15) Content-Type: text/plain; charset="iso-8859-1" HOP-COUNT: 1 X-MAILWATCH-INSTANCEID: 010200074070d2f6-91ca-41ea-ae11-4f228aaf4640 X-OriginalArrivalTime: 11 Jan 2002 15:54:31.0227 (UTC) FILETIME=[41D5B8B0:01C19AB8] > > All other patches are bug fixes or small corrections to > make Cygwin behave more consistent. > > Yeah, I was talking only about AST related stuff. If a patch > has nothing to do with AST, go ahead. But be aware that we will > discuss it and it still could be rejected, of course. That's > one of the most frustrating situations when contributing to an > OSS project for the first time but we all had to go through it. It's not the first time I'm contributing to a project, but the first time to Cygwin. > > Are the issues cleared now? > > It would be good if *you* are thinking they are cleared. If you're > feeling to move on thin ice with one of your patches, just hold this > part back. Please understand, we *want* to trust our contributors. For me everything's clear now. The only offending patch is the $SHELL thing, which I'll be leaving out. I'll start moving my patches to the latest CVS sources tomorrow. 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/