All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
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 11:48:19 +0200	[thread overview]
Message-ID: <8736liit24.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190511072049.2w7pp723iszp3gra@localhost.localdomain> (G. Branden Robinson's message of "Sat, 11 May 2019 17:20:52 +1000")

* 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.

Thanks,
Florian

  reply	other threads:[~2019-05-13  9:48 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 [this message]
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
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=8736liit24.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=g.branden.robinson@gmail.com \
    --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 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.