From: nick black <dankamongmen@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] console_codes.4: ffix
Date: Mon, 21 Mar 2022 04:33:24 -0400 [thread overview]
Message-ID: <Yjg4VHMhrabggl88@schwarzgerat.orthanc> (raw)
In-Reply-To: <20220320160217.gws42lklp6ishzub@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
G. Branden Robinson left as an exercise for the reader:
> I have some suggestions for further improvement, but please don't gate
> the patch application on these.
always good to hear from you, GBR. i replied to alejandro's
request with the original, not wanting to mess with (and then
test) groff right at the moment, but i've saved your
animadversions. i've got a patch outstanding for the linux
console right now, and once it lands, i'll need come back and
modify this page again (indeed, that's why i was looking at it
in the first place). i'll effect your suggestions then, thanks!
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-03-21 8:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 6:48 [patch] console_codes.4: ffix nick black
2022-01-17 17:30 ` Alejandro Colomar (man-pages)
2022-01-19 17:05 ` nick black
2022-01-25 17:35 ` nick black
[not found] ` <CAN4uE+p-uKzHNYry2YhCMfEFBQ2jUqpDAGx=+eha01w-L4fAjg@mail.gmail.com>
2022-03-20 16:02 ` G. Branden Robinson
2022-03-20 18:15 ` Alejandro Colomar (man-pages)
2022-03-21 8:30 ` nick black
2022-03-22 12:27 ` Alejandro Colomar (man-pages)
2022-03-22 12:56 ` nick black
2022-03-22 12:59 ` Alejandro Colomar (man-pages)
2022-03-22 13:01 ` nick black
2022-03-21 8:33 ` nick black [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=Yjg4VHMhrabggl88@schwarzgerat.orthanc \
--to=dankamongmen@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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