From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <dev@sethm.id.au>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 0/1] man/man2/*: Update history of syscalls H-M
Date: Mon, 16 Feb 2026 14:57:06 +0100 [thread overview]
Message-ID: <aZMeuDza3H4tVbgu@devuan> (raw)
In-Reply-To: <cover.1771232583.git.dev@sethm.id.au>
[-- Attachment #1: Type: text/plain, Size: 6280 bytes --]
On 2026-02-16T21:44:09+1000, Seth McDonald wrote:
> Hi Alex,
Hi Seth,
> Apologies on my end also for my delayed response. I've made some large
> but hopefully beneficial changes to my email workflow – as can be seen
> with the different email address.
:)
> > This patch seems to be corrupt. [...] Probably another issue with
> > protonmail, I guess.
>
> Yeah at this point I give up with ProtonMail. I shouldn't have to fix
> all their issues for them just to send in a patch. Hopefully Fastmail
> serves me better.
So far it works. I could apply the patch.
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!
> Anyhow, this is just the patch for mincore(2) with a few minor
> adjustments on the commit message. I won't PGP sign it yet as I first
> want to ensure everything works before adding things on top. But if all
> is well, I'll continue to sign my patches with my more secure key:
>
> E9D1 26A5 F0D4 9DF7 792B C2E2 B4BF 4530 D39B 2D51
Ok.
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:
uid mcdonald_seth@pm.me <mcdonald_seth@pm.me>
sig cert c267b0020a900289 2024-12-06T06:53:33Z ____________________ ____________________ [selfsig]
uid Seth McDonald (email encryption) <mcdonald_seth@pm.me>
sig revok c267b0020a900289 2026-02-11T08:27:33Z ____________________ ____________________ [selfsig]
Is it intentionaly that you revoked the UID instead of the key? If you
want to revoke the entire key, you should probably use gpg(1)'s
--gen-revoke flag, which generates a revocation certificate for the
master key.
>
> 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. :)
Cheers,
Alex
>
> Seth McDonald (1):
> man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
>
> man/man2/mincore.2 | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> Range-diff against v1:
> 1: d109f3dc06e2 < -: ------------ man/man2/ioctl_eventpoll.2: HISTORY: ffix
> 2: 55de16b213bf < -: ------------ man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)
> 3: 17eacf0f2d3e < -: ------------ man/man2/link.2: HISTORY: Change order of linkat(2)
> 4: bec317b8ee88 < -: ------------ man/man2/link.2: HISTORY: Update POSIX appearances of link(2)
> 5: 2024c82a058d < -: ------------ man/man2/listen.2: HISTORY: Change order
> 6: bcf9f5113f3c < -: ------------ man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}
> 7: 2dd12d136bf0 < -: ------------ man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)
> 8: 817af323707e ! 1: b1b6f011a7d3 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
> @@ Metadata
> ## Commit message ##
> man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
>
> - mincore(2) was implemented in FreeBSD on 1995-10-21,[1] which was first
> + mincore(2) was implemented in FreeBSD on 1995-10-21,[1] and was first
> included in the FreeBSD 2.2 release on 1997-03.[2]
>
> - It was implemented in NetBSD on 1999-06-15,[3] which was first included
> - in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
> + It was implemented in NetBSD on 1999-06-15,[3] and was first included in
> + the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
> stating its intended inclusion in NetBSD 1.4.1).
>
> - It was implemented in OpenBSD on 2001-03-09,[5] which was first included
> + It was implemented in OpenBSD on 2001-03-09,[5] and was first included
> in the OpenBSD 2.9 release on 2001-06-01.[6]
>
> All other listed systems are taken at face value and rearranged in
> chronological-ish order.
>
> [1] Dyson, John (21 Oct 1995). "Implement mincore system call."
> - FreeBSD source tree (Git repository).
> - <https://cgit.freebsd.org/src/commit/?id=02c04a2f6c83ee28ed637d120296d04da8f03372>
> + FreeBSD source tree (Git repository). Commit
> + 02c04a2f6c83ee28ed637d120296d04da8f03372.
> [2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
> <https://www.freebsd.org/releases>
> [3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested
> 9: 8b25a256e60f < -: ------------ man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)
> 10: 347e36c11666 < -: ------------ man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)
> 11: d3da8260e1bc < -: ------------ man/man2/mknod.2: HISTORY: Change order of mknodat(2)
> 12: b0feda20f21d < -: ------------ man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
> 13: 32bd25fd3630 < -: ------------ man/man2/mknod.2: STANDARDS: Update
> 14: 67bf0c1aa133 < -: ------------ man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)
> 15: 57292b4f60c4 < -: ------------ man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
> 16: b8f4e6fa54e7 < -: ------------ man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
> 17: 4e1acc0f5e00 < -: ------------ man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
> 18: 024ce32c9da5 < -: ------------ man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)
> 19: 975e61bea29f < -: ------------ man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)
> 20: 86e7c24b1428 < -: ------------ man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)
> 21: d106bca86ec1 < -: ------------ man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)
>
> base-commit: e2cc229b7551a63bb51853c849ce1a9e95946637
> --
> 2.53.0.1
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-16 13:57 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 ` Alejandro Colomar [this message]
2026-02-17 12:37 ` [PATCH v2 0/1] man/man2/*: Update history of syscalls H-M Seth McDonald
2026-02-17 12:51 ` Alejandro Colomar
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=aZMeuDza3H4tVbgu@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