From: Vincent Bernat <vincent-5wNQGcxKXm8AvxtiuMwx3w@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] recv.2: remove duplicate paragraph for MSG_ERRQUEUE
Date: Sat, 31 Dec 2016 14:08:28 +0100 [thread overview]
Message-ID: <m3bmvs9rg3.fsf@luffy.cx> (raw)
In-Reply-To: <3cb21035-4bc7-da18-febb-e2a919ba02c0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Michael Kerrisk's message of "Sat, 31 Dec 2016 11:27:32 +0100")
❦ 31 décembre 2016 11:27 +0100, "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> :
>> The removed paragraph is identical to the one a few lines above.
>
> Gosh! The duplication was injected back in man-pages-1.34 (2000)!
> Back in man-pages-1.33, it was the second instance only that was
> present, so I'm inclined to remove the other instance (opposite
> of your patch). What do you think?
I think both solutions are fine.
--
Use debugging compilers.
- The Elements of Programming Style (Kernighan & Plauger)
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-12-31 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 21:33 [PATCH] recv.2: remove duplicate paragraph for MSG_ERRQUEUE Vincent Bernat
[not found] ` <20161230213328.31980-1-vincent-5wNQGcxKXm8AvxtiuMwx3w@public.gmane.org>
2016-12-31 10:27 ` Michael Kerrisk (man-pages)
[not found] ` <3cb21035-4bc7-da18-febb-e2a919ba02c0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-31 13:08 ` Vincent Bernat [this message]
[not found] ` <m3bmvs9rg3.fsf-PWwKhitvBKI@public.gmane.org>
2016-12-31 19:34 ` 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=m3bmvs9rg3.fsf@luffy.cx \
--to=vincent-5wnqgcxkxm8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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