From: Herbert Xu <herbert@gondor.apana.org.au>
To: Forest <forestix@sonic.net>
Cc: dash@vger.kernel.org
Subject: Re: [PATCH] man page: redirection operators: fix swapped stdin/stdout
Date: Sat, 6 Apr 2024 14:23:01 +0800 [thread overview]
Message-ID: <ZhDqRT0zVzK7Fur0@gondor.apana.org.au> (raw)
In-Reply-To: <hpl58htt4cqjtgkt4lvqus3fpc8jc5fdls@4ax.com>
On Mon, May 16, 2022 at 04:02:24PM -0700, Forest wrote:
> The Redirections section incorrectly claimed that <& replaces stdout
> and >& replaces stdin. Swapped them to make it read correctly.
>
> Ref:
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_05
>
> Both errors were followed by extra text that looked like remains of a
> mostly-deleted sentence. Removed those.
> ---
> src/dash.1 | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2024-04-06 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 23:02 [PATCH] man page: redirection operators: fix swapped stdin/stdout Forest
2024-04-06 6:23 ` Herbert Xu [this message]
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=ZhDqRT0zVzK7Fur0@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dash@vger.kernel.org \
--cc=forestix@sonic.net \
/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).