From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Joe Damato <jdamato@fastly.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ioctl_epoll.2: New page describing epoll ioctl(2)
Date: Tue, 11 Jun 2024 10:42:33 -0500 [thread overview]
Message-ID: <20240611154233.3rapmsl2futdtdf7@illithid> (raw)
In-Reply-To: <kmuodpe6ijgk6g2lsjiggg3d6kdi5tv433jso54jxz2mxsvtqr@nlipunv5stt7>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
At 2024-06-11T16:22:28+0200, Alejandro Colomar wrote:
> Hmmm, so we should \e => \[rs]. Thanks! I'll try to prepare a sed
> script for it.
Cool!
> BTW, how are you doing with MR.sed? :)
I have not returned to the problem since last we spoke about it.
Working up the steam to tackle the staged-sed-attack on syscalls.2
tables again.
I will risk surrendering a hostage to fortune by venturing that MR.sed
_itself_ is already pretty well tested. It's getting that table ready
for MR.sed to go to work on it that is the devilish detail.
I am conscious that groff 1.23.0's first anniversary is nigh...
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-11 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 23:12 [PATCH v2 0/1] ioctl_epoll.2: Add epoll ioctl documentation Joe Damato
2024-06-10 23:12 ` [PATCH v2 1/1] ioctl_epoll.2: New page describing epoll ioctl(2) Joe Damato
2024-06-10 23:45 ` Alejandro Colomar
2024-06-11 0:29 ` Joe Damato
2024-06-11 8:54 ` Alejandro Colomar
2024-06-11 12:24 ` G. Branden Robinson
2024-06-11 14:22 ` Alejandro Colomar
2024-06-11 15:42 ` G. Branden Robinson [this message]
2024-06-11 16:34 ` Joe Damato
2024-06-11 17:14 ` Alejandro Colomar
2024-06-11 17:28 ` Joe Damato
2024-06-11 17:43 ` Alejandro Colomar
2024-06-11 17:58 ` Joe Damato
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=20240611154233.3rapmsl2futdtdf7@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=jdamato@fastly.com \
--cc=linux-man@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