From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215971] dd(1p) manpage contains empty ASCII to EBDIC tables
Date: Sat, 14 May 2022 15:12:48 +0000 [thread overview]
Message-ID: <bug-215971-11311-9aDFHTTGcy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215971-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215971
--- Comment #3 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
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
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-14 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-05-14 18:07 ` bugzilla-daemon
[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
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=bug-215971-11311-9aDFHTTGcy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 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.