unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.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, 29 Jul 2019 21:07:44 +0200	[thread overview]
Message-ID: <1906e1af-961c-adee-b08a-7daf8663b56d@gmail.com> (raw)
In-Reply-To: <20190511072049.2w7pp723iszp3gra@localhost.localdomain>

Hi Branden,

On 5/11/19 9:20 AM, G. Branden Robinson wrote:
> ...plus a patch with some suggested wording fixes.
> 
> ...plus a patch with some suggestions on improving the formatting and
> markup.

Sorry for the late reply. I actually applied some of your
changes a few days back (they're already in Git).

You often have good inputs, but your idiosyncratic submission
style does make it harder than necessary for me to deal with
that input. Please:

* One patch per mail
* Patches best inline; if you are worried your mailer may
  break the patch, then both inline and as an attachment.
* Your patch 3 does so many things at the same time that it's
  impossible to apply. Some of the things I agree with. Others
  not. 
* Some of your points in patch 3 are really suggestions
  suggestions for global changes in the manual pages.
  Obviously, they would need discussion, and shouldn't
  be done piecemeal, page at a time. I made some of the
  uncontroversial changes from this patch manually.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      parent reply	other threads:[~2019-07-29 19:07 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
2019-07-29 19:07 ` Michael Kerrisk (man-pages) [this message]

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1906e1af-961c-adee-b08a-7daf8663b56d@gmail.com \
    --to=mtk.manpages@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).