public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ram Gupta <ram.gupta5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux mailing-list
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: man pages for a specific kernel version
Date: Mon, 4 Jul 2011 02:51:40 -0500	[thread overview]
Message-ID: <20110704075140.GA24541@elie> (raw)
In-Reply-To: <AANLkTi=0+Z-vxqG11JMCX3uscqvGZniOL9zgWjU7JA76-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi,

Ram Gupta wrote:

> Does any one know for a way to get accurate man pages for a particular
> kernel version?
[...]
> As kernel keeps evolving man pages keep
> changing too

Sorry for a late response.  The intent is for the man-pages package to
document all kernel versions.  So when there are relevant differences
between versions that it does not explain, do please feel free to let
us know (ideally in the form of a patch, but a friendly comment is
fine, too).

Of course, like most documentation, these manpages are not perfect, so
if you need reliable information I'd suggest looking at the kernel
source.

Good luck,
Jonathan
--
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

  parent reply	other threads:[~2011-07-04  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  2:01 man pages for a specific kernel version Ram Gupta
     [not found] ` <AANLkTi=0+Z-vxqG11JMCX3uscqvGZniOL9zgWjU7JA76-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-19  9:44   ` Stefan Puiu
     [not found]     ` <AANLkTim=F5vFrGUT1dAi2mGeK5c3QHtWvuLL3+W8PQDy-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-19 12:32       ` Ram Gupta
2011-07-04  7:51   ` Jonathan Nieder [this message]
2011-09-11 14:28     ` Michael Kerrisk

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=20110704075140.GA24541@elie \
    --to=jrnieder-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ram.gupta5-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