public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <dev@sethm.id.au>, linux-man@vger.kernel.org
Subject: Re: [PATCH v2 0/1] man/man2/*: Update history of syscalls H-M
Date: Tue, 17 Feb 2026 13:51:22 +0100	[thread overview]
Message-ID: <aZRjzZ6XNrudqDyH@devuan> (raw)
In-Reply-To: <019c6b7c-ba8d-72e1-be96-ab6e6b8eb535@sethm.id.au>

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

Hi Seth,

On 2026-02-17T22:37:28+1000, Seth McDonald wrote:
> Hi Alex,
> 
> On Mon, 16 Feb 2026 at 14:57:06 +0100, Alejandro Colomar wrote:
> > I personally use Migadu <https://migadu.com/>.  I've had a very good
> > experience with them, and they're very quick in fixing any bugs I report
> > to them.  If Fastmail works fine for you, that's great!
> 
> I'm actually quite surprised I didn't come across them.  I tried looking
> at every email provider (even considered Purelymail, which I believe is
> currently a 2-3 person project).  Migadu do look great from their
> website, so I'll keep them in mind as a good backup.
> 
> > BTW, the ubuntu keyserver shows the existence of a non-revoked key that
> > is probably old?
> > 
> > 	pub (4)eddsa263/82b9620e53d0a1ae2d696111c267b0020a900289 2024-12-06T06:53:33Z
> > 
> > It contains two UIDs, one of which is revoked, but the other is not
> > revoked:
> [...]
> > Is it intentionaly that you revoked the UID instead of the key?
> 
> That actually was intentional.  The two signatures on my key are of the
> keys I used with my Proton emails; I signed it to show that I'm indeed
> the same person despite the different email address.
> 
> I added the second UID to imply that of the two keys, if someone wanted
> to send me encrypted email, they should use the one whose UID states
> "email encryption".  But since I'm no longer planning on those being my
> main email addresses, I revoked the "email encryption" UID.  But my
> Proton address does still use that key, so I didn't revoke the whole
> thing.

Ahh, makes sense.

> 
> > > Let me know if it's still corrupt, and I'll ̶k̶i̶c̶k̶ ̶m̶y̶ ̶P̶C calmly figure out
> > > what's going on.
> > 
> > It worked.  :)
> 
> Well that's certainly a relief!
> 
> Btw, did the strikethrough text render correctly for you?

Yup, it looks correct on mutt(1) and neomutt(1).


Have a lovely day!
Alex

>  It renders as
> strikethrough for me on mutt(1) and vim(1), but it looks -l-i-k-e- 
> -t-h-i-s on the lore.kernel.org archive.
> 
> Take care,
> 	Seth McDonald.
> 
> -- 
> E9D1 26A5 F0D4 9DF7 792B  C2E2 B4BF 4530 D39B 2D51



-- 
<https://www.alejandro-colomar.es>

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

      reply	other threads:[~2026-02-17 12:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 12:28 [PATCH v1 00/21] man/man2/*: Update history of syscalls H-M Seth McDonald
2026-01-26 12:28 ` [PATCH v1 01/21] man/man2/ioctl_eventpoll.2: HISTORY: ffix Seth McDonald
2026-01-26 12:28 ` [PATCH v1 02/21] man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2) Seth McDonald
2026-01-26 12:28 ` [PATCH v1 03/21] man/man2/link.2: HISTORY: Change order of linkat(2) Seth McDonald
2026-01-26 12:28 ` [PATCH v1 04/21] man/man2/link.2: HISTORY: Update POSIX appearances of link(2) Seth McDonald
2026-01-26 12:28 ` [PATCH v1 05/21] man/man2/listen.2: HISTORY: Change order Seth McDonald
2026-01-26 12:28 ` [PATCH v1 06/21] man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE} Seth McDonald
2026-01-26 18:28   ` G. Branden Robinson
2026-01-26 12:29 ` [PATCH v1 07/21] man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 08/21] man/man2/mincore.2: HISTORY: Update appearances of mincore(2) Seth McDonald
2026-02-10 23:50   ` Alejandro Colomar
2026-01-26 12:29 ` [PATCH v1 09/21] man/man2/mkdir.2: HISTORY: Change order of mkdirat(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 10/21] man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 11/21] man/man2/mknod.2: HISTORY: Change order of mknodat(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 12/21] man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 13/21] man/man2/mknod.2: STANDARDS: Update Seth McDonald
2026-01-26 12:29 ` [PATCH v1 14/21] man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2) Seth McDonald
2026-01-26 12:29 ` [PATCH v1 15/21] man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2) Seth McDonald
2026-01-26 12:30 ` [PATCH v1 16/21] man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix Seth McDonald
2026-01-26 12:30 ` [PATCH v1 17/21] man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2) Seth McDonald
2026-01-26 12:30 ` [PATCH v1 18/21] man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2) Seth McDonald
2026-01-26 12:30 ` [PATCH v1 19/21] man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2) Seth McDonald
2026-01-26 12:30 ` [PATCH v1 20/21] man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2) Seth McDonald
2026-01-26 12:30 ` [PATCH v1 21/21] man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2) Seth McDonald
2026-01-26 18:38 ` the origin of mkdir(2) (was: [PATCH v1 00/21] man/man2/*: Update history of syscalls H-M) G. Branden Robinson
2026-02-11  0:04 ` [PATCH v1 00/21] man/man2/*: Update history of syscalls H-M Alejandro Colomar
2026-02-16 11:44 ` [PATCH v2 0/1] " Seth McDonald
2026-02-16 11:45   ` [PATCH v2 1/1] man/man2/mincore.2: HISTORY: Update appearances of mincore(2) Seth McDonald
2026-02-16 13:41     ` Alejandro Colomar
2026-02-16 13:57   ` [PATCH v2 0/1] man/man2/*: Update history of syscalls H-M Alejandro Colomar
2026-02-17 12:37     ` Seth McDonald
2026-02-17 12:51       ` Alejandro Colomar [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=aZRjzZ6XNrudqDyH@devuan \
    --to=alx@kernel.org \
    --cc=dev@sethm.id.au \
    --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