Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 11 Jan 2004 15:08:58 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Unix pipes implemented successfully Message-ID: <20040111200858.GA18960@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <55216.212.0.200.4.1073846861.mtc@mail.moldtelecom.md> <6.0.1.1.0.20040111140418.037e01f8@127.0.0.1> <55258.212.0.200.4.1073851049.mtc@mail.moldtelecom.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@cygwin.com On Sun, Jan 11, 2004 at 09:57:29PM +0200, linamat@moldtelecom.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/