linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] pldd.1: Document glibc's unbreakage of tool.
Date: Mon, 13 May 2019 16:34:07 +0200	[thread overview]
Message-ID: <5CD9805F.4040601@bfs.de> (raw)
In-Reply-To: <8736liit24.fsf@oldenburg2.str.redhat.com>



Am 13.05.2019 11:48, schrieb Florian Weimer:
> * G. Branden Robinson:
> 
>>  .SH BUGS
>> -Since glibc 2.19,
>> +From glibc 2.19 to 2.29,
>>  .B pldd
>> -is broken: it just hangs when executed.
>> -.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=18035
>> -It is unclear if it will ever be fixed.
>> +was broken: it just hung when executed.
>> +.\" glibc commit 1a4c27355e146b6d8cc6487b998462c7fdd1048f
>> +This problem was fixed in glibc 2.30.
> 
> I'm not sure if it makes sense to document this in the manual page.  I
> expect that the fix will propagate to affected distributions fairly
> quickly, now that it is available upstream.  It's certainly more likely
> that users will receive a glibc update with the fix than a manpage
> update with this change.
> 

IMHO it should be noted in the BUGS section.
You can not rely that you have always the lastest version of libc
(at least i do not have) but you may notice a different behavior
and it is simply very helpful to have a hint that certain versions
are broken. (if someone cares: my problem was with a64l. It suddenly
changed behavior ...)

just my 2 cents,
re,
 wh

  parent reply	other threads:[~2019-05-13 14:34 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)
2019-07-29 19:27             ` Carlos O'Donell
2019-05-13 14:34   ` walter harms [this message]
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=5CD9805F.4040601@bfs.de \
    --to=wharms@bfs.de \
    --cc=libc-alpha@sourceware.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;
as well as URLs for NNTP newsgroup(s).