On Feb 8 17:35, Michael Haubenwallner wrote: > > On 2/8/19 2:28 PM, Corinna Vinschen wrote: > > > > I pushed your forkable branch to master, btw. Would you mind to do the > > honors in the ;rease notes at cygwin/release/3.0 and doc/new-features.xml? > > Do you mean like this? > > /haubi/ > >From 0461e0a552caf0c58ab7999cfd2849c7180f7d30 Mon Sep 17 00:00:00 2001 > From: Michael Haubenwallner > Date: Fri, 8 Feb 2019 15:38:56 +0100 > Subject: [PATCH] forkables: add release notes > > --- > winsup/cygwin/release/3.0 | 10 ++++++++++ > winsup/doc/new-features.xml | 12 ++++++++++++ > 2 files changed, 22 insertions(+) > > diff --git a/winsup/cygwin/release/3.0 b/winsup/cygwin/release/3.0 > index 4cd422a56..ef45e9f9d 100644 > --- a/winsup/cygwin/release/3.0 > +++ b/winsup/cygwin/release/3.0 > @@ -66,6 +66,16 @@ What changed: > Native Windows processes not started by Cygwin processes are mapped > into the range beyond 65535. > > +- Limited to executables and dlls located on the very same NTFS partition > + as the Cygwin installation itself, and disabled by default, fork(2) now > + is able to recover from when the executable or any dll required to load > + into the new child process was removed or replaced since being loaded > + into the parent process, or a dll with different content is found in the > + parent process' current directory. To enable this recovery feature, the > + following command has to be executed once per Cygwin installation, with > + subsequent shutdown of all Cygwin processes (or reboot), so the first > + Cygwin process does find this directory existing: > + $ mkdir --mode=a=rwxt /var/run/cygfork It's not bad but for release notes it's rather long. Any chance to get a more compact text? Also, please add a "Cygwin: " prefix to the log message summary. I'd like to distinguish CYgwin-only changes from newlib changes. Thanks, Corinna -- Corinna Vinschen Cygwin Maintainer