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: Sun, 11 Jan 2004 15:08:58 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Unix pipes implemented successfully Message-ID: <20040111200858.GA18960@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <55216 DOT 212 DOT 0 DOT 200 DOT 4 DOT 1073846861 DOT mtc AT mail DOT moldtelecom DOT md> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040111140418 DOT 037e01f8 AT 127 DOT 0 DOT 0 DOT 1> <55258 DOT 212 DOT 0 DOT 200 DOT 4 DOT 1073851049 DOT mtc AT mail DOT moldtelecom DOT md> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55258.212.0.200.4.1073851049.mtc@mail.moldtelecom.md> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Sun, Jan 11, 2004 at 09:57:29PM +0200, linamat AT moldtelecom DOT md wrote: >>Sorry, but no. The CVS version of cygwin already has a stub of a fifo >>implementation and the device/fhandler stuff is much different than >>1.5.5. > >But if I change the patch to be compliant with last CVS, should you change >the answer? Sorry but it's unlikely. As I said, there is already a start of an implementation for this which I am unlikely to want to throw out. I expect to have a working fifo implementation in a couple of releases. It's the next thing I'll work on after fixing the signal/thread problems in the current CVS. -- 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/