public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Yaowei Bai <bywxiaobai@163.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: Mon, 9 Mar 2015 11:34:50 -0500	[thread overview]
Message-ID: <20150309163450.GD10815@treble.redhat.com> (raw)
In-Reply-To: <20150309153902.GA7742@bbox>

On Mon, Mar 09, 2015 at 11:39:02PM +0800, Yaowei Bai wrote:
> On Fri, Mar 06, 2015 at 09:59:38AM -0600, Josh Poimboeuf wrote:
> > On Tue, Mar 03, 2015 at 10:08:02PM +0800, Yaowei Bai wrote:
> > > As we have moved to 4.x, it should be reflected in README.
> > > 
> > > Signed-off-by: Yaowei Bai <bywxiaobai@163.com>
> > > ---
> > >  README | 34 +++++++++++++++++-----------------
> > >  1 file changed, 17 insertions(+), 17 deletions(-)
> > 
> > Remove all references to Linux version numbers (except for the examples)
> > in the README so we won't have to update it again for Linux 5.0.
> 
> It sounds great, but i think that would be more easily comprehensible with version
> numbers in README, especially for the ones who are not familiar with Linux kernel
> very much. Meanwhile, does it make sense for a software without version number
> in release file?

Personally I don't think the "4.x" numbers add anything to the
understanding of the document.  And anyway, Linus doesn't update them to
4.0, 4.1, etc per release, so it's not a real release file.

> On the other hand, it only need *one* patch to update the version
> numbers in README every several years, i.e. about 8 years and 4 years
> for 3.x and 4.x, respectively.

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.

-- 
Josh

  reply	other threads:[~2015-03-09 16:35 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 [this message]
2015-03-10 14:17       ` Yaowei Bai

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=20150309163450.GD10815@treble.redhat.com \
    --to=jpoimboe@redhat.com \
    --cc=bywxiaobai@163.com \
    --cc=corbet@lwn.net \
    --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