From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/3] tee.2: ffix
Date: Mon, 3 Jan 2022 17:49:50 +0100 [thread overview]
Message-ID: <cb677780-c486-29ba-5928-5d9a56c1f233@gmail.com> (raw)
In-Reply-To: <a59610f1d397bf532e4ce46481f439ac089fb05e.1641224016.git.nabijaczleweli@nabijaczleweli.xyz>
On 1/3/22 16:33, наб wrote:
> ---
наб, patch applied!
Thanks, Alex
> man2/tee.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/tee.2 b/man2/tee.2
> index d2ceef331..14a927c93 100644
> --- a/man2/tee.2
> +++ b/man2/tee.2
> @@ -143,7 +143,7 @@ Here is an example of its use:
> .PP
> .in +4n
> .EX
> -$ \fBdate |./a.out out.log | cat\fP
> +$ \fBdate | ./a.out out.log | cat\fP
> Tue Oct 28 10:06:00 CET 2014
> $ \fBcat out.log\fP
> Tue Oct 28 10:06:00 CET 2014
--
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2022-01-03 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 15:33 [PATCH 1/3] tee.2: ffix наб
2022-01-03 15:34 ` [PATCH 2/3] tee.2: use proper types in example, declare variables at point-of-use наб
2022-01-03 16:25 ` Alejandro Colomar (man-pages)
2022-01-03 15:34 ` [PATCH 3/3] tee.2: always fail after perror(), use for(;;) instead of do{}while(1) наб
2022-01-03 16:40 ` Alejandro Colomar (man-pages)
2022-01-03 17:03 ` [PATCH v2 2/4] tee.2: use proper types in example наб
2022-01-03 17:27 ` Alejandro Colomar (man-pages)
2022-01-03 17:35 ` наб
2022-01-03 17:51 ` Alejandro Colomar (man-pages)
2022-01-03 17:03 ` [PATCH v2 3/4] tee.2: use for(;;) instead of do{}while(1) наб
2022-01-03 17:03 ` [PATCH v2 4/4] tee.2: always fail after perror() in example наб
2022-01-03 16:49 ` Alejandro Colomar (man-pages) [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=cb677780-c486-29ba-5928-5d9a56c1f233@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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.