Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API

Hi Branden,

On 2/15/23 03:21, G. Branden Robinson wrote:

At 2023-02-15T02:52:03+0100, Alejandro Colomar wrote:

quoted

On 2/15/23 02:20, G. Branden Robinson wrote:

quoted

[CC list violently trimmed; for those who remain, this is mostly man
page style issues]

Ironically, you trimmed linux-man@  :D

I didn't!  It wasn't present in the mail to which I repled.

Hmm, you're right, Mathieu didn't CC linux-man@.  I guessed somewhere
in that big list it would be there, but it wasn't.  Thanks for CCing it.

This did puzzle me.  I guess it was an oversight.  You might want to
re-send that message of yours, and/or Mathieu's, if it lacked it too.

Or maybe it doesn't matter because lore.kernel.org finds all.  I just
used it to track down an exchange between Michael Kerrisk and me that
GMail refused to find even though it was in my inbox.  It showed me only
one thread, didn't highlight the specific message that it thought
matched, and showed me the _wrong_ thread on top of everything else.
The word "constraint" was in the thread I wanted, not in the one I
didn't, and even when I quoted it I was served up an incorrect match.

Which reminds me that I hate searching in the groff@ archives.  It's not
because of the search engine, but because of the thread view.  You are
artificially restricted to a given month, and you can't see entire threads
in the search engine.  Is there anything similar to lore for groff@?
Other GNU projects can now be searched at <https://inbox.sourceware.org/>
such as <https://inbox.sourceware.org/libc-alpha/>, but groff@ isn't there
:(

Cheers,

Alex

Clearly their AI efforts are going swimmingly.> 
Regards,
Branden

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5