[bootlin/training-materials updates] master: common/kernel-clone-master-and-stable: reword (73502b00)

[Thomas Petazzoni]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/73502b002f71f1fc10354531215cbd37c54c90e3

>---------------------------------------------------------------

commit 73502b002f71f1fc10354531215cbd37c54c90e3
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Thu Sep 22 14:56:56 2022 +0200

    common/kernel-clone-master-and-stable: reword
    
    The text says that the repo from Torvalds would only contains a
    "target that moves every day", which is completely incorrect. The repo
    from Torvalds has tags, for each main kernel release. Those tags don't
    move.
    
    So the reason to use stable versions is not about "not using something
    that moves every day".
    
    Reword the whole section.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


>---------------------------------------------------------------

73502b002f71f1fc10354531215cbd37c54c90e3
 common/kernel-clone-master-and-stable.tex | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/common/kernel-clone-master-and-stable.tex b/common/kernel-clone-master-and-stable.tex
index 4d4737d0..065e7566 100644
--- a/common/kernel-clone-master-and-stable.tex
+++ b/common/kernel-clone-master-and-stable.tex
@@ -37,16 +37,12 @@ newer Linux version.
 
 \section{Accessing stable releases}
 
-Having the Linux kernel development sources is great, but when you are
-creating products, you prefer to avoid working with a target that moves
-every day.
+The Linux kernel repository from Linus Torvalds contains all the main
+releases of Linux, but not the stable versions: they are maintained by
+a separate team, and hosted in a separate repository.
 
-That's why we need to use the {\em stable} releases of the Linux
-kernel.
-
-Fortunately, with \code{git}, you won't have to clone an entire source
-tree again. All you need to do is add a reference to a {\em remote}
-tree, and fetch only the commits which are specific to that remote tree.
+We will add this separate repository as another {\em remote} to be
+able to use the stable releases:
 
 {\footnotesize
 \begin{verbatim}