[PATCH] README: Update version number reference

[PATCH] README: Update version number reference

[Jeff Kirsher]

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

Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
 README | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/README b/README
index a24ec89..67fc7a8 100644
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
-        Linux kernel release 3.x <http://kernel.org/>
+        Linux kernel release 4.x <http://kernel.org/>
 
-These are the release notes for Linux version 3.  Read them carefully,
+These are the release notes for Linux version 4.  Read them carefully,
 as they tell you what this is all about, explain how to install the
 kernel, and what to do if something goes wrong. 
 
@@ -62,11 +62,11 @@ INSTALLING the kernel source:
    directory where you have permissions (eg. your home directory) and
    unpack it:
 
-     gzip -cd linux-3.X.tar.gz | tar xvf -
+     gzip -cd linux-4.X.tar.gz | tar xvf -
 
    or
 
-     bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
+     bzip2 -dc linux-4.X.tar.bz2 | tar xvf -
 
    Replace "X" with the version number of the latest kernel.
 
@@ -75,16 +75,16 @@ INSTALLING the kernel source:
    files.  They should match the library, and not get messed up by
    whatever the kernel-du-jour happens to be.
 
- - You can also upgrade between 3.x releases by patching.  Patches are
+ - You can also upgrade between 4.x releases by patching.  Patches are
    distributed in the traditional gzip and the newer bzip2 format.  To
    install by patching, get all the newer patch files, enter the
-   top level directory of the kernel source (linux-3.X) and execute:
+   top level directory of the kernel source (linux-4.X) and execute:
 
-     gzip -cd ../patch-3.x.gz | patch -p1
+     gzip -cd ../patch-4.x.gz | patch -p1
 
    or
 
-     bzip2 -dc ../patch-3.x.bz2 | patch -p1
+     bzip2 -dc ../patch-4.x.bz2 | patch -p1
 
    Replace "x" for all versions bigger than the version "X" of your current
    source tree, _in_order_, and you should be ok.  You may want to remove
@@ -92,13 +92,13 @@ INSTALLING the kernel source:
    that there are no failed patches (some-file-name# or some-file-name.rej).
    If there are, either you or I have made a mistake.
 
-   Unlike patches for the 3.x kernels, patches for the 3.x.y kernels
+   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
    (also known as the -stable kernels) are not incremental but instead apply
-   directly to the base 3.x kernel.  For example, if your base kernel is 3.0
-   and you want to apply the 3.0.3 patch, you must not first apply the 3.0.1
-   and 3.0.2 patches. Similarly, if you are running kernel version 3.0.2 and
-   want to jump to 3.0.3, you must first reverse the 3.0.2 patch (that is,
-   patch -R) _before_ applying the 3.0.3 patch. You can read more on this in
+   directly to the base 4.x kernel.  For example, if your base kernel is 4.0
+   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
+   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
+   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
+   patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
    Documentation/applying-patches.txt
 
    Alternatively, the script patch-kernel can be used to automate this
@@ -120,7 +120,7 @@ INSTALLING the kernel source:
 
 SOFTWARE REQUIREMENTS
 
-   Compiling and running the 3.x kernels requires up-to-date
+   Compiling and running the 4.x kernels requires up-to-date
    versions of various software packages.  Consult
    Documentation/Changes for the minimum version numbers required
    and how to get updates for these packages.  Beware that using
@@ -137,12 +137,12 @@ BUILD directory for the kernel:
    place for the output files (including .config).
    Example:
 
-     kernel source code: /usr/src/linux-3.X
+     kernel source code: /usr/src/linux-4.X
      build directory:    /home/name/build/kernel
 
    To configure and build the kernel, use:
 
-     cd /usr/src/linux-3.X
+     cd /usr/src/linux-4.X
      make O=/home/name/build/kernel menuconfig
      make O=/home/name/build/kernel
      sudo make O=/home/name/build/kernel modules_install install
-- 
1.9.3

Re: [PATCH] README: Update version number reference

[Jonathan Corbet]

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

Re: [PATCH] README: Update version number reference

[Jeff Kirsher]

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

On Thu, 2015-03-19 at 15:11 -0600, Jonathan Corbet wrote:
> 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.

I am slammed with Intel wired Ethernet patches currently, so I do not
mind if someone else wants to wants to take the lead on this.  I like
the idea of making this version agnostic so that this type of
modification does not need to be made anytime a major version change is
made.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]