linux-man.vger.kernel.org archive mirror
 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: Fri, 17 May 2019 17:44:41 +0200	[thread overview]
Message-ID: <87y335m6fq.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190513141746.mail6ny43wh4t5oj@localhost.localdomain> (G. Branden Robinson's message of "Tue, 14 May 2019 00:17:48 +1000")

* G. Branden Robinson:

>> I'm not sure if it makes sense to document this in the manual page.
>
> It might not; another resonable approach might be to nuke the "Bugs"
> section of the man page entirely.  However, see below.
>
>> I expect that the fix will propagate to affected distributions fairly
>> quickly, now that it is available upstream.
>
> True for fast-moving distributions; as I noted in the commit message,
> Debian 10 has already got it backported to its glibc 2.29.

I'm pretty sure Debian 10 does not use glibc 2.28.

My point is that the glibc change will get backported, but any man-pages
change will not, so it will be quite some time until the latter shows up
on developer workstations.  And due to glibc backporting, the version
information there will be misleading.

Thanks,
Florian

  reply	other threads:[~2019-05-17 15:44 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 [this message]
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=87y335m6fq.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 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).