linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
Date: Wed, 15 Feb 2023 04:07:59 +0100	[thread overview]
Message-ID: <a5eea3fa-11be-21f6-4e7b-617cb7ff428d@gmail.com> (raw)
In-Reply-To: <20230215022150.pxuhdbx2zdwjpems@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1842 bytes --]

Hi Branden,

On 2/15/23 03:21, G. Branden Robinson wrote:
> At 2023-02-15T02:52:03+0100, Alejandro Colomar wrote:
>> On 2/15/23 02:20, G. Branden Robinson wrote:
>>> [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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-15  3:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 19:54 [PATCH 1/1] rseq.2: New man page for the rseq(2) API Mathieu Desnoyers
2023-02-14 22:29 ` Alejandro Colomar
2023-02-15  1:20   ` G. Branden Robinson
2023-02-15  1:52     ` Alejandro Colomar
2023-02-15  2:21       ` G. Branden Robinson
2023-02-15  3:07         ` Alejandro Colomar [this message]
2023-02-15 16:44           ` Mathieu Desnoyers
2023-02-15 17:09     ` Mathieu Desnoyers
2023-02-15 17:12       ` Mathieu Desnoyers
2023-02-15 17:16       ` Alejandro Colomar
2023-02-15 18:58         ` Mathieu Desnoyers

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=a5eea3fa-11be-21f6-4e7b-617cb7ff428d@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.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;
as well as URLs for NNTP newsgroup(s).