public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yaowei Bai <bywxiaobai@163.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: corbet@lwn.net, trivial@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: make the README agnostic to version numbers
Date: Tue, 10 Mar 2015 22:17:02 +0800	[thread overview]
Message-ID: <20150310141702.GA6607@bbox> (raw)
In-Reply-To: <20150309163450.GD10815@treble.redhat.com>

On Mon, Mar 09, 2015 at 11:34:50AM -0500, Josh Poimboeuf wrote:
> Personally I don't think the "4.x" numbers add anything to the
> understanding of the document.

Maybe the reason you think so is that you are quite familiar with the kernel,
but we should also take care of the ones who are not familiar with it. For example,
usually, README is the first file for these people to read, with version numbers in README,
then one will acquire which era the kenrel is currently in.

> And anyway, Linus doesn't update them to
> 4.0, 4.1, etc per release, so it's not a real release file.
> 

Even so, i still believe that's helpful with version number references in README.

> 
> True, changing this file every 4 years or so isn't a big deal.  But
> Linux doesn't do _big_ changes any more, so whether its "3.x", "4.x", or
> "x.y", the use cases and release notes are the same.

Well, personally, i really don't think so.

--
Yaowei

> 
> -- 
> Josh


      reply	other threads:[~2015-03-10 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 14:08 [PATCH 1/2] Update version number references in README Yaowei Bai
2015-03-03 14:08 ` [PATCH 2/2] README: Change gzip/bzip2 to xz compression format Yaowei Bai
2015-03-19 21:12   ` Jonathan Corbet
2015-03-06 15:59 ` [PATCH] README: make the README agnostic to version numbers Josh Poimboeuf
2015-03-09 15:39   ` Yaowei Bai
2015-03-09 16:34     ` Josh Poimboeuf
2015-03-10 14:17       ` Yaowei Bai [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=20150310141702.GA6607@bbox \
    --to=bywxiaobai@163.com \
    --cc=corbet@lwn.net \
    --cc=jpoimboe@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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