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: Mon, 12 Jan 2004 12:37:02 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Unix pipes implementation Message-ID: <20040112173702.GB12821@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <1251 DOT 212 DOT 0 DOT 200 DOT 22 DOT 1073923082 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: <1251.212.0.200.22.1073923082.mtc@mail.moldtelecom.md> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Mon, Jan 12, 2004 at 05:58:02PM +0200, linamat AT Moldtelecom DOT md wrote: >>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. >Ok. > >>I expect to have a working fifo implementation in a couple of releases. >How much of time could it take? It would probably take me a couple of days once I'm out from under the mountain of work that I'm currently experiencing. >Can I do something to decrease this delay? Cause I want to have newest >cygwin version and Unix FIFO support already. This is one of those cases where there is really no good solution for you. I don't see this happening soon and I really don't have the time to try to shepard you, or anyone, through the current fifo code so that I can fill you in on the way I want to see this done. cgf -- 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/