From: Helge Kreutzmann <debian@helgefjell.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page motd.5
Date: Wed, 1 Nov 2023 15:49:44 +0000 [thread overview]
Message-ID: <ZUJzmBx5ymZgBED2@meinfjell.helgefjelltest.de> (raw)
In-Reply-To: <ZUJy9p4iXH-t4OOy@debian>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Hello Alejandro,
Am Wed, Nov 01, 2023 at 04:47:02PM +0100 schrieb Alejandro Colomar:
> 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
> $
Then disregard this report and I need to check where this man page
actually comes from. Probably assigned here by error.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 15:49 UTC|newest]
Thread overview: 8+ 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
2023-11-01 15:49 ` Helge Kreutzmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:08 ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:07 ` Alejandro Colomar
2023-01-22 20:31 ` Helge Kreutzmann
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=ZUJzmBx5ymZgBED2@meinfjell.helgefjelltest.de \
--to=debian@helgefjell.de \
--cc=alx@kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).