From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] dtdiff: change to POSIX shell
Date: Thu, 1 Feb 2018 23:14:18 -0500 [thread overview]
Message-ID: <20180202041418.GD27582@vapier> (raw)
In-Reply-To: <20180110055718.GG19773-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On 10 Jan 2018 16:57, David Gibson wrote:
> On Wed, Jan 10, 2018 at 12:47:56AM -0500, Mike Frysinger wrote:
> > This changes from the bash-specific process substitution feature to
> > reading with pipes. It relies on /dev/fd or /proc/self/fd existing.
> >
> > URL: https://crbug.com/756559
> > Signed-off-by: Mike Frysinger <vapier-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>
> Yeah, sorry, replacing a dependency on a complex but widely available
> shell with a much more cryptic dependency on a Linux specific feature
> does not seem like a win to me.
bash's <(...) only works when the host supports either /dev/fd or /proc/self/fd,
so i don't think this is less portable. /dev/fd also isn't Linux-specific.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-02 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 5:47 [PATCH] dtdiff: change to POSIX shell Mike Frysinger
[not found] ` <20180110054756.23464-1-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2018-01-10 5:57 ` David Gibson
[not found] ` <20180110055718.GG19773-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2018-02-02 4:14 ` Mike Frysinger [this message]
2018-02-02 4:35 ` Kyle Evans
[not found] ` <CACNAnaESOk5Wb+Y1Sy2X3AuCqXFMj1QZ6_CFORTE=AcFRckM4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-05 18:31 ` Mike Frysinger
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=20180202041418.GD27582@vapier \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.