From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] more: fix control character display bug
Date: Fri, 20 Feb 2015 11:29:39 +0100 [thread overview]
Message-ID: <20150220102939.GA19430@ws.net.home> (raw)
In-Reply-To: <1422608050-28600-1-git-send-email-kerolasa@iki.fi>
On Fri, Jan 30, 2015 at 09:54:10AM +0100, Sami Kerola wrote:
> text-utils/more.c | 59 +++++++++++++++++++++++++------------------------------
> 1 file changed, 27 insertions(+), 32 deletions(-)
Does it make sense to apply this patch? I guess the issue is already
(also) fixed in you "more" branch at git hub, right?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-02-20 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 8:54 [PATCH] more: fix control character display bug Sami Kerola
2015-01-30 16:05 ` Sami Kerola
2015-02-02 10:35 ` Karel Zak
2015-01-30 20:18 ` Benno Schulenberg
2015-02-01 22:41 ` [PATCH 2/2] more: fix get_line() indentation Sami Kerola
2015-02-20 10:29 ` Karel Zak [this message]
2015-02-20 11:06 ` [PATCH] more: fix control character display bug Sami Kerola
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=20150220102939.GA19430@ws.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--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