public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@netscape.net>
To: insight@sources.redhat.com
Subject: Re: Patch to avoid using mkfifo under cygwin
Date: Tue, 17 Sep 2002 10:27:00 -0000	[thread overview]
Message-ID: <3D8765E4.8020003@netscape.net> (raw)

On Fri, Sep 13, 2002 at 11:07:38AM -0700, Keith Seitz wrote:
 >>On Fri, 13 Sep 2002, Mo DeJong wrote:
 >>>This was causing a failure in the Tcl test suite, but it
 >>>should not matter to anyone.  Since Cygwin will add the
 >>>feature soon, it seems fine to just leave it the way it
 >>>is.
 >>
 >>Ah, okay.  Thanks for the clarification.

 >Ditto.  Thanks, Mo.  This should be available soon when we
 >release "cygserver".

Is this mkfifo support "vaporware" or is it something that 
could be checked into the cygdaemon-branch for testing? 
IIRC, nothing was said to indicate that this was actually 
being fixed.  All I remember is that Robert said he was too 
busy and Max said he might look at it.  However, this is the 
first peep regarding the issue I heard since then.  Clue me 
in if I'm wrong.

Cheers,
Nicholas

             reply	other threads:[~2002-09-17 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 10:27 Nicholas Wourms [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-12 15:51 Patch to avoid using mkfifo under Cygwin Mo DeJong
2002-09-12 16:06 ` Patch to avoid using mkfifo under cygwin Christopher Faylor
2002-09-13  7:44 ` Patch to avoid using mkfifo under Cygwin Keith Seitz
2002-09-13  9:39   ` Patch to avoid using mkfifo under cygwin Christopher Faylor
2002-09-13  9:57     ` Keith Seitz
2002-09-13 11:01       ` Mo DeJong
2002-09-13 11:05         ` Keith Seitz
2002-09-13 14:32           ` Christopher Faylor
2002-09-13 12:22   ` Patch to avoid using mkfifo under Cygwin Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D8765E4.8020003@netscape.net \
    --to=nwourms@netscape.net \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).