linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Update version number references in README
@ 2015-03-01 14:01 Yaowei Bai
  2015-03-02  1:31 ` Ken Moffat
  0 siblings, 1 reply; 3+ messages in thread
From: Yaowei Bai @ 2015-03-01 14:01 UTC (permalink / raw)
  To: linux-kernel

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(-)

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.1



^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] Update version number references in README
  2015-03-01 14:01 [PATCH] Update version number references in README Yaowei Bai
@ 2015-03-02  1:31 ` Ken Moffat
  2015-03-03 13:30   ` 白耀伟
  0 siblings, 1 reply; 3+ messages in thread
From: Ken Moffat @ 2015-03-02  1:31 UTC (permalink / raw)
  To: Yaowei Bai; +Cc: linux-kernel

On Sun, Mar 01, 2015 at 10:01:16PM +0800, Yaowei Bai wrote:
> As we have moved to 4.x, it should be reflected in README.
> 

 Not something I can affect, but just a couple of comments on what
looks like a useful, but unadventurous, change :

1. Firing patches at the list, without copying them to a maintainer,
often means that they are ignored.  Perhaps this should be sent to
the trivial maintainer (unless the documentation maintainer thinks
this is within his area - I have not looked to see if anybody admits
to maintaining this).

2. Perhaps you should also mention .xz variants ?  Actually, on a
version of tar from the last few years, tar -xf
linux-4.X.tar.{gz,bz,xz} "just works".  But I'm sure that some people
who deliberately test on antique userspace (and perhaps people who
do not use gnu tar) might take a different view on that.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re:Re: [PATCH] Update version number references in README
  2015-03-02  1:31 ` Ken Moffat
@ 2015-03-03 13:30   ` 白耀伟
  0 siblings, 0 replies; 3+ messages in thread
From: 白耀伟 @ 2015-03-03 13:30 UTC (permalink / raw)
  To: Ken Moffat; +Cc: linux-kernel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1072 bytes --]


>1. Firing patches at the list, without copying them to a maintainer,
>often means that they are ignored.  Perhaps this should be sent to
>the trivial maintainer (unless the documentation maintainer thinks
>this is within his area - I have not looked to see if anybody admits
>to maintaining this).

'/scripts/get_maintainer.pl -f README' only yeilds LKML,yes, maybe this patch
should be sent to the trivial maintainer or the doc maintainer.

>
>2. Perhaps you should also mention .xz variants ?  Actually, on a

Will turn to xz, thx.

>version of tar from the last few years, tar -xf
>linux-4.X.tar.{gz,bz,xz} "just works".  But I'm sure that some people
>who deliberately test on antique userspace (and perhaps people who
>do not use gnu tar) might take a different view on that.
>
>ĸen
>-- 
>Nanny Ogg usually went to bed early. After all, she was an old lady.
>Sometimes she went to bed as early as 6 a.m.
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-03-03 14:35 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-01 14:01 [PATCH] Update version number references in README Yaowei Bai
2015-03-02  1:31 ` Ken Moffat
2015-03-03 13:30   ` 白耀伟

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).