public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin/main] Cygwin: document FIFO over NFS change
Date: Tue,  5 Sep 2023 08:46:25 +0000 (GMT)	[thread overview]
Message-ID: <20230905084625.1C3E8385843A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=2ab2e73c2c9602de98e218525d30149f0fb109ee

commit 2ab2e73c2c9602de98e218525d30149f0fb109ee
Author:     Corinna Vinschen <corinna@vinschen.de>
AuthorDate: Sat Aug 26 16:59:18 2023 +0200
Commit:     Corinna Vinschen <corinna@vinschen.de>
CommitDate: Mon Sep 4 10:41:06 2023 +0200

    Cygwin: document FIFO over NFS change
    
    Signed-off-by: Corinna Vinschen <corinna@vinschen.de>

Diff:
---
 winsup/cygwin/release/3.5.0 | 2 ++
 winsup/doc/new-features.xml | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/winsup/cygwin/release/3.5.0 b/winsup/cygwin/release/3.5.0
index cdb175797c52..dbbf8009d4a1 100644
--- a/winsup/cygwin/release/3.5.0
+++ b/winsup/cygwin/release/3.5.0
@@ -39,3 +39,5 @@ What changed:
 - posix_spawnp no longer falls back to starting the shell for unrecognized
   files as execvp.  For the reasoning, see
   https://www.austingroupbugs.net/view.php?id=1674
+
+- FIFOs now also work over NFS.
diff --git a/winsup/doc/new-features.xml b/winsup/doc/new-features.xml
index 98ca7f595c24..78b2dbafdc2e 100644
--- a/winsup/doc/new-features.xml
+++ b/winsup/doc/new-features.xml
@@ -58,6 +58,10 @@ posix_spawn_file_actions_addfchdir_np.
 New API calls: c8rtomb, c16rtomb, c32rtomb, mbrtoc8, mbrtoc16, mbrtoc32.
 </para></listitem>
 
+<listitem><para>
+FIFOs now also work over NFS.
+</para></listitem>
+
 </itemizedlist>
 
 </sect2>

                 reply	other threads:[~2023-09-05  8:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230905084625.1C3E8385843A@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=cygwin-cvs@sourceware.org \
    /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).