From: "Stéphane Aulery" <saulery@free.fr>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Shirley <diamond@nonado.net>,
dash@vger.kernel.org, 501566@bugs.debian.org
Subject: dash: details of redirection/duplication in manpage are reversed
Date: Tue, 11 Nov 2014 21:46:00 +0100 [thread overview]
Message-ID: <20141111204600.GA13252@free.fr> (raw)
In-Reply-To: <20141111150805.GA18820@gondor.apana.org.au>
Hello,
Le mardi 11 novembre 2014 à 11:08:05, Herbert Xu a écrit :
> On Tue, Nov 11, 2014 at 02:23:21PM +0100, Stephen Shirley wrote:
> >
> > "[n1]>&n2 Redirect standard output (or n1) to n2."
> >
> > It doesn't cover the case where n2 is later changed, and how n1 does
> > not follow this, but it's the simplest fix i see.
>
> Yes that sounds much better. Please send a patch.
Here is one. Stephen, the correction of the first line is abandoned?
[n1]<&n2 Duplicate standard input (or n1) from file descriptor n2.
Regards,
--
Stéphane Aulery
next prev parent reply other threads:[~2014-11-11 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 11:19 dash: details of redirection/duplication in manpage are reversed Stéphane Aulery
2014-11-10 13:24 ` Herbert Xu
2014-11-10 13:49 ` Stéphane Aulery
2014-11-11 13:23 ` Bug#501566: " Stephen Shirley
2014-11-11 14:19 ` Stephane Chazelas
2014-11-12 2:13 ` Herbert Xu
2014-11-11 15:08 ` Herbert Xu
2014-11-11 20:46 ` Stéphane Aulery [this message]
2014-11-11 20:47 ` Stéphane Aulery
2014-11-12 2:12 ` Herbert Xu
2014-11-12 11:09 ` Stéphane Aulery
2014-11-21 11:52 ` [MAN] Clarify two redirection mechanisms saulery
2014-12-01 10:04 ` Herbert Xu
2014-12-01 12:27 ` Stephane Chazelas
2014-11-18 23:27 ` Bug#501566: dash: details of redirection/duplication in manpage are reversed Stéphane Aulery
2014-11-18 23:46 ` Stéphane Aulery
2014-11-19 0:00 ` Stéphane CHAZELAS
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=20141111204600.GA13252@free.fr \
--to=saulery@free.fr \
--cc=501566@bugs.debian.org \
--cc=dash@vger.kernel.org \
--cc=diamond@nonado.net \
--cc=herbert@gondor.apana.org.au \
/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 NNTP newsgroup(s).