public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: cygwin-patches@cygwin.com
Subject: [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks
Date: Mon, 21 Feb 2022 14:36:16 +0100 (CET)	[thread overview]
Message-ID: <cover.1645450518.git.johannes.schindelin@gmx.de> (raw)

These symbolic links are crucial e.g. to support process substitution (Bash's
very nice `<(SOME-COMMAND)` feature).

For various reasons, it is a bit cumbersome (or impossible) to generate these
symbolic links in all circumstances where Git for Windows wants to use its
close fork of the Cygwin runtime.

Therefore, let's just handle these symbolic links as implicit, virtual ones.

If there is appetite for it, I wonder whether we should do something similar
for `/dev/shm` and `/dev/mqueue`? Are these even still used in Cygwin?

Johannes Schindelin (2):
  Implicitly support the /dev/fd symlink and friends
  Regenerate devices.cc

 winsup/cygwin/Makefile.am        |    1 +
 winsup/cygwin/devices.cc         | 1494 ++++++++++++++++--------------
 winsup/cygwin/devices.h          |    3 +-
 winsup/cygwin/devices.in         |    4 +
 winsup/cygwin/dtable.cc          |    3 +
 winsup/cygwin/fhandler.h         |   28 +
 winsup/cygwin/fhandler_dev_fd.cc |   53 ++
 7 files changed, 879 insertions(+), 707 deletions(-)
 create mode 100644 winsup/cygwin/fhandler_dev_fd.cc


base-commit: ba7b912feba3178e530a484afea4cb127e7f2ae7
Published-As: https://github.com/dscho/msys2-runtime/releases/tag/virtual-dev-fd-cygwin-v1
Fetch-It-Via: git fetch https://github.com/dscho/msys2-runtime virtual-dev-fd-cygwin-v1

--
2.35.1


             reply	other threads:[~2022-02-21 13:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 13:36 Johannes Schindelin [this message]
2022-02-21 13:36 ` [PATCH 1/2] Implicitly support the /dev/fd symlink and friends Johannes Schindelin
2022-02-21 13:36 ` [PATCH 2/2] Regenerate devices.cc Johannes Schindelin
2022-02-22 12:34 ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks Corinna Vinschen
2022-02-25 15:46   ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin, stdout, stderr} symlinks Johannes Schindelin
2022-02-28  9:24     ` Corinna Vinschen
2022-02-28  9:57       ` Corinna Vinschen
2023-03-28  8:34         ` Johannes Schindelin
2022-02-25 18:35 ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks Brian Inglis
2023-03-28  8:36   ` Johannes Schindelin

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=cover.1645450518.git.johannes.schindelin@gmx.de \
    --to=johannes.schindelin@gmx.de \
    --cc=cygwin-patches@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).