From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Carlos O'Donell <carlos@redhat.com>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, Florian Weimer <fweimer@redhat.com>,
linux-man <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] pldd.1: Document glibc's unbreakage of tool.
Date: Mon, 29 Jul 2019 21:18:15 +0200 [thread overview]
Message-ID: <3f28f3b3-8fde-2bfb-51bc-6958511ee666@gmail.com> (raw)
In-Reply-To: <CAEMqeSrCMFZ8GQU=kR_+KXaqnd9m-3qUSQk1PNZ2xHjZ_YVHFg@mail.gmail.com>
On 5/17/19 5:56 PM, Carlos O'Donell wrote:
> On Fri, May 17, 2019 at 11:51 AM G. Branden Robinson
> <g.branden.robinson@gmail.com> wrote:
>> What would you prefer? That the man page not document the bug at all?
>> Was it a mistake in your view to have added the information about the
>> bug to the man page in the first place?
>
> I think having the glibc upstream version information is useful.
And so do I. My compromise in such cases is to write something like:
this:
BUGS
From glibc 2.19 to 2.29, pldd was broken: it just hung when exe‐
cuted. This problem was fixed in glibc 2.30, and the fix has been
backported to earlier glibc versions in some distributions.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2019-07-29 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 7:20 [PATCH] pldd.1: Document glibc's unbreakage of tool G. Branden Robinson
2019-05-13 9:48 ` Florian Weimer
2019-05-13 14:17 ` G. Branden Robinson
2019-05-17 15:44 ` Florian Weimer
2019-05-17 15:51 ` G. Branden Robinson
2019-05-17 15:56 ` Carlos O'Donell
2019-05-20 16:58 ` Joseph Myers
2019-07-29 19:32 ` Michael Kerrisk (man-pages)
2019-07-29 19:18 ` Michael Kerrisk (man-pages) [this message]
2019-07-29 19:27 ` Carlos O'Donell
2019-05-13 14:34 ` walter harms
2019-07-29 19:07 ` Michael Kerrisk (man-pages)
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=3f28f3b3-8fde-2bfb-51bc-6958511ee666@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=libc-alpha@sourceware.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 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 NNTP newsgroup(s).