From: Karel Zak <kzak@redhat.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH v2 1/3] write: correctly handle wide characters
Date: Fri, 17 Mar 2023 11:50:28 +0100 [thread overview]
Message-ID: <20230317105028.sgu5722ry2kqzdsx@ws.net.home> (raw)
In-Reply-To: <3b606a113f36256be6486bd3130944acf88777d7.1678893303.git.nabijaczleweli@nabijaczleweli.xyz>
On Wed, Mar 15, 2023 at 04:16:31PM +0100, наб wrote:
> include/carefulputc.h | 60 +++++++++++++++++++++++++++++++------------
> login-utils/last.c | 4 +--
> term-utils/write.c | 25 +++++-------------
> 3 files changed, 52 insertions(+), 37 deletions(-)
Applied (all 3 patches), thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2023-03-17 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230315141649.d7d4ybcg3evyelpo@ws.net.home>
2023-03-15 15:16 ` [PATCH v2 1/3] write: correctly handle wide characters наб
2023-03-17 10:50 ` Karel Zak [this message]
2023-03-15 15:16 ` [PATCH v2 2/3] wall: convert homebrew buffering to open_memstream() наб
2023-03-15 15:16 ` [PATCH v2 3/3] wall: use fputs_careful() наб
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=20230317105028.sgu5722ry2kqzdsx@ws.net.home \
--to=kzak@redhat.com \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=util-linux@vger.kernel.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 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).