public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Martin Wege <martin.l.wege@gmail.com>
To: cygwin@cygwin.com
Cc: Corinna Vinschen via Cygwin-announce <cygwin-announce@cygwin.com>
Subject: NFS mkfifo support in cygwin 3.5.0 Re: [ANNOUNCEMENT] cygwin 3.4.9-1
Date: Thu, 7 Sep 2023 23:20:01 +0200	[thread overview]
Message-ID: <CANH4o6MSXBxMBsqgtWbNe9rPETNgY-D5QxJO9AsLwe+tm0WkDw@mail.gmail.com> (raw)
In-Reply-To: <announce.20230906172530.526501-1-corinna-cygwin@cygwin.com>

On Wed, Sep 6, 2023 at 5:27 PM Corinna Vinschen via Cygwin-announce
via Cygwin <cygwin@cygwin.com> wrote:
>
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygwin-3.4.9-1
> * cygwin-devel-3.4.9-1
> * cygwin-doc-3.4.9-1
>
> Bug Fixes
> ---------
>
> - Fix a bug introduced in cygwin 3.4.0 that switch_to_nat_pipe flag is
>   not cleared properly when non-cygwin app is terminated in the case
>   where pseudo console is not activated.
>
> - For the time being, disable creating special files using mknod/mkfifo
>   on NFS.
>   Addresses: https://cygwin.com/pipermail/cygwin/2023-August/254266.html

While I am unhappy that you disabled this for Cygwin 3.4.9-1, we
noticed that you added mkfifo support for Cygwin 3.5.0 in
https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=622fb0776ea333dd708ff312f08ec98311138fbe
🙏😁 :-)

Thanks

We are testing 3.5.0-0.423.g7ced682549ae.x86_64 - which includes
622fb0776ea333dd708ff312f08ec98311138fbe - right now, feedback will
come on Monday

Thanks,
Martin

  reply	other threads:[~2023-09-07 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 15:25 Corinna Vinschen via Cygwin-announce
2023-09-07 21:20 ` Martin Wege [this message]
2023-09-08  4:48   ` NFS mkfifo support in cygwin 3.5.0 " Cedric Blancher
2023-09-08 10:59     ` Corinna Vinschen
2023-09-08 20:31       ` Corinna Vinschen
2023-09-09 21:33         ` NFS mkfifo support in cygwin 3.5.0 Corinna Vinschen

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=CANH4o6MSXBxMBsqgtWbNe9rPETNgY-D5QxJO9AsLwe+tm0WkDw@mail.gmail.com \
    --to=martin.l.wege@gmail.com \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.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).