Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3B962D77.8050205@ece.gatech.edu>
Date: Wed, 05 Sep 2001 09:49:43 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: gp AT familiehaase DOT de
CC: cygwin-apps AT cygwin DOT com
Subject: Re: IPC stuff
References: <3B96255B DOT 10663 DOT 5620B7F AT localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Gerrit P. Haase wrote:

> Ludovic LANGE schrieb am 2001-09-05, 1:32:


   ^^^^^^^^^^^^^

Thanks for tracking him down.  (Now, if you could use those skills to 
find Paul Sokolovsky...).  Looks as though Chris' memory was correct; 
much of the cygipc code was derived from Linux (and therefore is 
multiply-copyrighted and practically unassignable for Cygwin inclusion).

So, Ludovic seems to agree that the best approach is to start over with 
independent code, and makes a few points about who should be allowed to 
contribute.  I think he's a bit cavalier about some stuff, but I'll wait 
for a verdict from the core developers before I begin work on 
*IPC*-related things in the new (and still vapor) cygwin-daemon.

FWIW, Corinna started off a good discussion about cygwin-daemon design 
issues on cygwin-developers...

--Chuck