linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	Michael Kerrisk <mtk.manpages@gmail.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: Fri, 17 May 2019 11:56:34 -0400	[thread overview]
Message-ID: <CAEMqeSrCMFZ8GQU=kR_+KXaqnd9m-3qUSQk1PNZ2xHjZ_YVHFg@mail.gmail.com> (raw)
In-Reply-To: <20190517155057.vr5uk6hfkyp44y3t@localhost.localdomain>

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.

Cheers,
Carlos.

  reply	other threads:[~2019-05-17 15:56 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 [this message]
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='CAEMqeSrCMFZ8GQU=kR_+KXaqnd9m-3qUSQk1PNZ2xHjZ_YVHFg@mail.gmail.com' \
    --to=carlos@redhat.com \
    --cc=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).