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] Cygwin: add "app execution aliases" treatment to release notes Date: Tue, 23 Mar 2021 15:58:56 +0000 (GMT) [thread overview] Message-ID: <20210323155856.F14C83861031@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=f578883232d578bd83132f1f94a7f6826a74048e commit f578883232d578bd83132f1f94a7f6826a74048e Author: Corinna Vinschen <corinna@vinschen.de> Date: Tue Mar 23 16:54:23 2021 +0100 Cygwin: add "app execution aliases" treatment to release notes Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/cygwin/release/3.2.0 | 4 ++++ winsup/doc/new-features.xml | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/winsup/cygwin/release/3.2.0 b/winsup/cygwin/release/3.2.0 index 421b94a98..828ef5610 100644 --- a/winsup/cygwin/release/3.2.0 +++ b/winsup/cygwin/release/3.2.0 @@ -46,6 +46,10 @@ What changed: - facl(2) now fails with EBADF on a file opened with O_PATH. +- Allow to start Windows Store executables via their "app execution + aliases". Handle these aliases (which are special reparse points) + as symlinks to the actual executables. + Bug Fixes --------- diff --git a/winsup/doc/new-features.xml b/winsup/doc/new-features.xml index d59fc12c4..5ec36e409 100644 --- a/winsup/doc/new-features.xml +++ b/winsup/doc/new-features.xml @@ -70,6 +70,12 @@ work. facl(2) now fails with EBADF on a file opened with O_PATH. </para></listitem> +<listitem><para> +- Allow to start Windows Store executables via their "app execution + aliases". Handle these aliases (which are special reparse points) + as symlinks to the actual executables. +</para></listitem> + </itemizedlist> </sect2>
reply other threads:[~2021-03-23 15:58 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=20210323155856.F14C83861031@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: linkBe 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).