public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@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: Tue, 14 Feb 2023 20:21:50 -0600	[thread overview]
Message-ID: <20230215022150.pxuhdbx2zdwjpems@illithid> (raw)
In-Reply-To: <82ced680-8c2c-75b7-4368-16e602353f32@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

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.

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.

Clearly their AI efforts are going swimmingly.

Regards,
Branden

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

  reply	other threads:[~2023-02-15  2:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230214195442.937586-1-mathieu.desnoyers@efficios.com>
     [not found] ` <669eb324-aef6-0583-c8a4-f54a93ee4d6d@gmail.com>
     [not found]   ` <20230215012054.twzw4k5et6hxvi2j@illithid>
2023-02-15  1:52     ` [PATCH 1/1] rseq.2: New man page for the rseq(2) API Alejandro Colomar
2023-02-15  2:21       ` G. Branden Robinson [this message]
2023-02-15  3:07         ` Alejandro Colomar
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=20230215022150.pxuhdbx2zdwjpems@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@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