From: Jonathan Corbet <corbet@lwn.net>
To: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nathan Scott <nathans@redhat.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] Docs: proc: fix kernel version
Date: Tue, 21 Apr 2015 06:13:54 -0600 [thread overview]
Message-ID: <20150421061354.582a430d@lwn.net> (raw)
In-Reply-To: <1429584503-2530-1-git-send-email-chenhanxiao@cn.fujitsu.com>
On Mon, 20 Apr 2015 22:48:23 -0400
Chen Hanxiao <chenhanxiao@cn.fujitsu.com> wrote:
Thank you for working to update the documentation! That said, though, I
have a question and a request with regard to this particular change.
> -Table 1-2: Contents of the status files (as of 3.20.0)
> +Table 1-2: Contents of the status files (as of 4.1)
That file is full of weird version numbers; is there a reason why you want
to change that one in particular? The 2.6.8-rc3 reference immediately
afterward doesn't seem more worthy of protection.
This file is dramatically out of date in general. Rather than change the
version number at the head of the list of status files, why not update the
list to match current reality? There are a lot of things missing.
Failing that, I would entertain a patch that simply removes most of the
version numbers from this file; I don't think they provide any useful
information, and I certainly don't see the value of occasionally tweaking
them forward.
Thanks,
jon
next prev parent reply other threads:[~2015-04-21 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 2:48 Chen Hanxiao
2015-04-21 12:13 ` Jonathan Corbet [this message]
2015-04-22 2:58 ` Chen, Hanxiao
2015-05-07 15:55 ` Jonathan Corbet
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=20150421061354.582a430d@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=chenhanxiao@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@redhat.com \
--cc=trivial@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
all inboxes | Powered by JetHome®