From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page motd.5
Date: Wed, 1 Nov 2023 16:47:02 +0100 [thread overview]
Message-ID: <ZUJy9p4iXH-t4OOy@debian> (raw)
In-Reply-To: <ZUJaY2kc5oHbc9TR@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi Helge,
On Wed, Nov 01, 2023 at 02:02:11PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: B<issue>(5) B<pam_motd>(8) → B<issue>(5), B<pam_motd>(8)
>
> "B<login>(1), B<issue>(5) B<pam_motd>(8)"
I don't understand the report. I don't find any pam_motd reference in
motd(5). See below:
$ grep pam_motd man5/motd.5
$ git log -S pam_motd -- man5/motd.5
$
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Issue in man page motd.5 Helge Kreutzmann
2023-11-01 15:47 ` Alejandro Colomar [this message]
2023-11-01 15:49 ` Helge Kreutzmann
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-08-31 11:33 ` Alejandro Colomar
2025-08-31 11:42 ` Helge Kreutzmann
2025-08-31 12:11 ` Alejandro Colomar
2025-08-31 12:56 ` Mario Blättermann
2025-08-31 13:18 ` Alejandro Colomar
2025-08-31 13:30 ` G. Branden Robinson
2025-08-31 13:37 ` Helge Kreutzmann
2025-08-31 13:44 ` Alejandro Colomar
2025-08-31 13:46 ` G. Branden Robinson
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 11:10 ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:07 ` Alejandro Colomar
2023-01-22 20:31 ` Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:08 ` 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=ZUJy9p4iXH-t4OOy@debian \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.