mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Yaowei Bai <bywxiaobai@163.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] README: Update version number reference
Date: Thu, 19 Mar 2015 15:11:58 -0600	[thread overview]
Message-ID: <20150319151158.55f42b3b@lwn.net> (raw)
In-Reply-To: <1424838176-12614-1-git-send-email-jeffrey.t.kirsher@intel.com>

On Tue, 24 Feb 2015 20:22:56 -0800
Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:

> When 4.0 is released, the README should reflect the new numbering.

OK, I've applied this because it came in first.  There were two other
contenders, from Yaowei Bai and Josh Poimbeuf (copied) that all did
mostly the same thing, but Josh was trying to make it
version-independent. 

May I point something out, though?  All three of you did something like:

-     bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
+     bzip2 -dc linux-4.X.tar.bz2 | tar xvf -

without noticing the fact that .bz2 files haven't been available from
kernel.org for a while.  Much less that installation from tarballs must
be getting rare, and people shouldn't put them in /usr/src in any case.

In other words, this file is pretty crufty in quite a few ways that just
tweaking the version number will not fix.  Given enough time I'll try to
take a swing at it, but if anybody wants to bring it into the current
era, that would be most welcome.

Thanks,

jon

  reply	other threads:[~2015-03-19 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  4:22 Jeff Kirsher
2015-03-19 21:11 ` Jonathan Corbet [this message]
2015-03-19 21:20   ` Jeff Kirsher

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=20150319151158.55f42b3b@lwn.net \
    --to=corbet@lwn.net \
    --cc=bywxiaobai@163.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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®