From: Otto Ebeling <oebeling-YEAOTlfEoH7f77WrBdCPMDwVj7d+iGoU@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch] Update move_pages(2) manpage to match kernel change
Date: Wed, 30 Aug 2017 10:27:41 +0100 [thread overview]
Message-ID: <97d77ae058e1c886de4f63499677c73b@github.mail.kapsi.fi> (raw)
In-Reply-To: <CAKgNAkh8mcyVuvMYqitB1OO3eo3_fy3gg_fakGmQ+34sYjz1GQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Michael,
>> Not sure how to word this in a man page - maybe something like "4.13,
>> and
>> updated versions of 3.18, 4.12, 4.4, and 4.9". What do you think?
>
> The cross-product if individual patches that hit stable and the
> various stable versions is just too complex too track in man pages, so
> I do not even try...
OK, I'm fine with that too - so let's make the change in the form you
proposed?
Thanks,
Otto
--
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
prev parent reply other threads:[~2017-08-30 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 21:05 [patch] Update move_pages(2) manpage to match kernel change Otto Ebeling
[not found] ` <2646ef81-62da-13d5-2793-18149df3659b@gmail.com>
[not found] ` <2646ef81-62da-13d5-2793-18149df3659b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-22 8:14 ` Otto Ebeling
[not found] ` <94ae97965e44ee23301c31a114577315-YEAOTlfEoH7f77WrBdCPMDwVj7d+iGoU@public.gmane.org>
2017-08-22 22:58 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh8mcyVuvMYqitB1OO3eo3_fy3gg_fakGmQ+34sYjz1GQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-30 9:27 ` Otto Ebeling [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97d77ae058e1c886de4f63499677c73b@github.mail.kapsi.fi \
--to=oebeling-yeaotlfeoh7f77wrbdcpmdwvj7d+igou@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