Michael Opdenacker michael.opdenacker at free-electrons.com
Thu Sep 19 15:01:41 CEST 2013

Repository : git://git.free-electrons.com/training-materials.git

On branch  : kernel-ng

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

Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Sep 19 15:00:02 2013 +0200

Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>

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

1 file changed, 23 insertions(+)

index 164dd51..f811301 100644
@@ -59,5 +59,28 @@ Of course, if you directly ran \code{git clone}, you won't have run
\code{git pull} today. You may run \code{git pull} every morning though,
or at least every time you need an update of the upstream source tree.

+\section{Accessing stable releases}
+
+Having the Linux kernel development sources is great, but when you are
+creating products, you prefer to avoid working with target that moves
+every day.
+
+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.
+
+\begin{verbatim}
+git fetch stable
+\end{verbatim}
+