From: Alejandro Colomar <alx.manpages@gmail.com>
To: bugzilla-daemon@kernel.org
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [Bug 215971] dd(1p) manpage contains empty ASCII to EBDIC tables
Date: Sat, 14 May 2022 17:12:43 +0200 [thread overview]
Message-ID: <4150b49f-cb87-d065-3159-da7c67a5e9b2@gmail.com> (raw)
In-Reply-To: <bug-215971-216477-6uQkdMd68z@https.bugzilla.kernel.org/>
Hi Ben
On 5/14/22 17:04, bugzilla-daemon@kernel.org wrote:
> Hi Alex,
>
> I was under the impression that the maintainer of man-pages-posix had access to
> the roff(7) sources:
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages-posix.git/tree/README,
> but perhaps I misunderstood this. Apparently the sources can be obtained by
> contacting The Open Group?
>
I guess maybe Michael Kerrisk has the sources; I don't.
<https://www.kernel.org/doc/man-pages/maintaining.html>
And every time I've tried to set up an accout in the open group website,
I've found it a nightmare of redirections, logins, and accounts, so I
gave up trying.
Sorry :/
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next parent reply other threads:[~2022-05-14 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215971-216477@https.bugzilla.kernel.org/>
[not found] ` <bug-215971-216477-6uQkdMd68z@https.bugzilla.kernel.org/>
2022-05-14 15:12 ` Alejandro Colomar [this message]
2022-05-12 18:15 [Bug 215971] New: dd(1p) manpage contains empty ASCII to EBDIC tables bugzilla-daemon
2022-05-14 14:52 ` [Bug 215971] " bugzilla-daemon
2022-05-14 15:04 ` bugzilla-daemon
2022-05-14 15:12 ` bugzilla-daemon
2022-05-14 18:07 ` bugzilla-daemon
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=4150b49f-cb87-d065-3159-da7c67a5e9b2@gmail.com \
--to=alx.manpages@gmail.com \
--cc=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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