[bootlin/training-materials updates] master: Kernel course: remove git slides and lab (44d1cca8)
Michael Opdenacker
michael.opdenacker at bootlin.com
Mon May 10 21:37:46 CEST 2021
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/44d1cca85190445c1a45245faa9715340bd11140
>---------------------------------------------------------------
commit 44d1cca85190445c1a45245faa9715340bd11140
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Mon May 10 21:37:46 2021 +0200
Kernel course: remove git slides and lab
- Not elaborate enough anyway
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
44d1cca85190445c1a45245faa9715340bd11140
agenda/linux-kernel-agenda.tex | 12 -
agenda/linux-kernel-fr-agenda.tex | 10 -
agenda/linux-kernel-online-agenda.tex | 12 -
agenda/linux-kernel-online-fr-agenda.tex | 10 -
labs/kernel-git/kernel-git.tex | 143 ---------
mk/linux-kernel.mk | 4 -
slides/kernel-git-content/git-gui.png | Bin 98813 -> 0 bytes
slides/kernel-git-content/git-kernel-org.png | Bin 154333 -> 0 bytes
slides/kernel-git-content/gitk.png | Bin 207883 -> 0 bytes
slides/kernel-git-content/kernel-git-content.tex | 381 -----------------------
slides/kernel-git-content/progit2.png | Bin 117397 -> 0 bytes
slides/kernel-git-lab/kernel-git-lab.tex | 9 -
slides/kernel-git-title/kernel-git-title.tex | 1 -
13 files changed, 582 deletions(-)
diff --git a/agenda/linux-kernel-agenda.tex b/agenda/linux-kernel-agenda.tex
index 3ac01826..e4c6d648 100644
--- a/agenda/linux-kernel-agenda.tex
+++ b/agenda/linux-kernel-agenda.tex
@@ -498,20 +498,8 @@ Embedded Linux kernel and driver development training\\
\begin{itemize}
\item DMA
\item mmap
- \item Introduction to Git
\end{itemize}
}
-{Demo - If time left}
-{
- \begin{itemize}
- \item Get familiar with git by contributing to a real
- project: the Linux kernel
- \item Send your patches to the maintainers and
- mailing lists.
- \end{itemize}
-}
-
-\feagendaonecolumn
{Questions and Answers}
{
\begin{itemize}
diff --git a/agenda/linux-kernel-fr-agenda.tex b/agenda/linux-kernel-fr-agenda.tex
index 07036e94..d89b231b 100644
--- a/agenda/linux-kernel-fr-agenda.tex
+++ b/agenda/linux-kernel-fr-agenda.tex
@@ -521,18 +521,8 @@ Session de 5 jours
\begin{itemize}
\item DMA
\item mmap
- \item Introduction à Git
\end{itemize}
}
-{TP - S'il reste du temps}
-{
- \begin{itemize}
- \item Se familiariser avec git en contribuant à un vrai projet: le noyau Linux
- \item Envoyez vos patches aux mainteneurs et aux listes de discussion.
- \end{itemize}
-}
-
-\feagendaonecolumn
{Questions / réponses}
{
\begin{itemize}
diff --git a/agenda/linux-kernel-online-agenda.tex b/agenda/linux-kernel-online-agenda.tex
index 5bb03f54..93704b90 100644
--- a/agenda/linux-kernel-online-agenda.tex
+++ b/agenda/linux-kernel-online-agenda.tex
@@ -475,20 +475,8 @@ On-line seminar
\begin{itemize}
\item DMA
\item mmap
- \item Introduction to Git
\end{itemize}
}
-{Demo - If time left}
-{
- \begin{itemize}
- \item Get familiar with git by contributing to a real
- project: the Linux kernel
- \item Send your patches to the maintainers and
- mailing lists.
- \end{itemize}
-}
-
-\feagendaonecolumn
{Questions and Answers}
{
\begin{itemize}
diff --git a/agenda/linux-kernel-online-fr-agenda.tex b/agenda/linux-kernel-online-fr-agenda.tex
index 4aa24106..6465c31b 100644
--- a/agenda/linux-kernel-online-fr-agenda.tex
+++ b/agenda/linux-kernel-online-fr-agenda.tex
@@ -506,18 +506,8 @@ Séminaire de formation en ligne
\begin{itemize}
\item DMA
\item mmap
- \item Introduction à Git
\end{itemize}
}
-{Démo - S'il reste du temps}
-{
- \begin{itemize}
- \item Se familiariser avec git en contribuant à un vrai projet: le noyau Linux
- \item Envoyez vos patches aux mainteneurs et aux listes de discussion.
- \end{itemize}
-}
-
-\feagendaonecolumn
{Questions / réponses}
{
\begin{itemize}
diff --git a/labs/kernel-git/kernel-git.tex b/labs/kernel-git/kernel-git.tex
deleted file mode 100644
index 0de46498..00000000
--- a/labs/kernel-git/kernel-git.tex
+++ /dev/null
@@ -1,143 +0,0 @@
-\subchapter{Going further: Git}{Objective: Get familiar with git by contributing to the Linux kernel}
-
-After this lab, you will be able to:
-
-\begin{itemize}
-\item Explore the history of a Git repository.
-\item Create a branch and use it to make improvements to the Linux kernel sources.
-\item Make your first contribution to the official Linux kernel sources.
-\item Rework and reorganize the commits done in your branch.
-\item Work with a remote tree.
-\end{itemize}
-
-\section{Setup}
-
-Go to your kernel source tree in \code{~/linux-kernel-labs/src/linux}
-
-\section{Exploring the history}
-
-With \code{git log}, look at the list of changes that have been made on the scheduler
-(in \code{kernel/sched/}).
-
-With \code{git log}, look at the list of changes and their associated
-patches, that have been made on the ATMEL serial driver
-(\code{drivers/tty/serial/atmel_serial.c}) between the versions 3.0
-and 3.1 of the kernel.
-
-With \code{git diff}, look at the differences between \code{fs/jffs2/}
-(which contains the JFFS2 filesystem driver) in 3.0 and 3.1.
-
-With \code{gitk}, look at the full history of the UBIFS filesystem (in
-\code{fs/ubifs/}).
-
-On the {\em cgit} interface of Linus Torvalds tree, available at
-\url{https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/},
-search all commits that have been done by Bootlin (hint: use
-the search engine by author).
-
-\section{Modify the Linux kernel sources}
-
-Find something to modify in the Linux kernel sources. Here are ideas:
-
-\begin{itemize}
-\item Choose an ARM defconfig file, apply it, run \code{make} and fix compile warnings
-\item Implement changes recommended in the Kernel Janitors page:
- \url{https://kernelnewbies.org/KernelJanitors/Todo}
-\item Run the \code{scripts/checkpatch.pl} command on a subdirectory of the Linux tree.
- You can do that with \url{https://bootlin.com/labs/run-checkpatch}
-\item Look for spelling mistakes in documentation, or classical mistakes like "the the", "a a"...
-\item Look for unnecessary includes in C source files.
-\item Device tree sources: simplify them by replacing nodes that are
- instantiated again in the \code{.dts} files (with their location
- in the tree) by a {\em phandle} to a definition in the \code{.dtsi} file
- (simpler because you don't have to repeat the location in the tree).
- Make sure that the new DT is equivalent by decompiling and comparing the old DTB
- and the new DTB (\code{dtc -I dtb}).
-\item Run \code{apt install coccinelle} and \code{make coccicheck}
- and try to propose fixes for the reported bugs (\code{coccinelle}
- can propose patches too, but they need to be reviewed by humans
- before submission.
-
-\end{itemize}
-
-Before making changes, create a new branch and move into it.
-
-Now, implement your changes, and commit them, following instructions
-in the slides for contributing to the Linux kernel.
-
-\section{Share your changes}
-
-Generate the patch series corresponding to your two changes using
-\code{git format-patch}.
-
-Then, to send your patches, you will need to use your own SMTP server, either your company's
-if it is accessible from where you are, or the SMTP server available for a personal e-mail
-accounts (Google Mail for example, which has the advantage that your e-mail can be read
-from anywhere).
-
-Configure git to tell it about your SMTP settings (user, password, port...).
-
-Once this is done, send the patches to yourself using \code{git send-email}.
-
-\section{Check your changes}
-
-Before a final submission to the Linux kernel maintainers and community, you
-should run the below checks:
-
-\begin{itemize}
-\item Run \code{scripts/checkpatch.pl} on each of your patches.
- Fix the errors and warnings that you get, and commit them.
-\item Make sure that your modified code compiles with no warning,
- and if possible, that it also executes well.
-\item Make sure that the commit titles and messages are appropriate
- (see our guidelines in the slides)
-\end{itemize}
-
-If you made any change, use \code{git rebase --interactive master} to
-reorder, group, and edit your changes when needed.
-
-Don't hesitate to ask your instructor for help. The instructor will also
-be happy to have a final look at your changes before you send them for real.
-
-\section{Send your patches to the community}
-
-Find who to send the patches to, and send them for real.
-
-Don't be afraid to do this. The Linux kernel already includes changes
-performed during previous Bootlin kernel sessions!
-
-Unless you have done this before, you made your first contribution
-to the Linux kernel sources! We hope that our explanations and the power
-of git will incite you to make more contributions by yourself.
-
-\section{Tracking another tree}
-
-Say you want to work on the realtime Linux tree, you'll then add this
-tree to the trees you're tracking:
-
-\small
-\begin{verbatim}
-git remote add realtime \
- git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
-\end{verbatim}
-\normalsize
-
-A \code{git fetch} will fetch the data for this tree. Of course, Git
-will optimize the storage, and will not store everything that's common
-between the two trees. This is the big advantage of having a single
-local repository to track multiple remote trees, instead of having
-multiple local repositories.
-
-We can then switch to the master branch of the realtime tree:
-
-\begin{verbatim}
-git checkout realtime/master
-\end{verbatim}
-
-Or look at the difference between the scheduler code in the official
-tree and in the realtime tree:
-
-\begin{verbatim}
-git diff master..realtime/master kernel/sched/
-\end{verbatim}
-
diff --git a/mk/linux-kernel.mk b/mk/linux-kernel.mk
index e336ad38..35fa5c51 100644
--- a/mk/linux-kernel.mk
+++ b/mk/linux-kernel.mk
@@ -54,9 +54,6 @@ LINUX_KERNEL_SLIDES = \
kernel-backup-slides-title \
kernel-driver-development-dma \
kernel-driver-development-mmap \
- kernel-git-title \
- kernel-git-content \
- kernel-git-lab
LINUX_KERNEL_LABS = setup \
kernel-sources-download \
@@ -72,4 +69,3 @@ LINUX_KERNEL_LABS = setup \
kernel-serial-interrupt \
kernel-locking \
kernel-debugging \
- kernel-git
diff --git a/slides/kernel-git-content/git-gui.png b/slides/kernel-git-content/git-gui.png
deleted file mode 100644
index e6c463bc..00000000
Binary files a/slides/kernel-git-content/git-gui.png and /dev/null differ
diff --git a/slides/kernel-git-content/git-kernel-org.png b/slides/kernel-git-content/git-kernel-org.png
deleted file mode 100644
index 044831c6..00000000
Binary files a/slides/kernel-git-content/git-kernel-org.png and /dev/null differ
diff --git a/slides/kernel-git-content/gitk.png b/slides/kernel-git-content/gitk.png
deleted file mode 100644
index 22490b3a..00000000
Binary files a/slides/kernel-git-content/gitk.png and /dev/null differ
diff --git a/slides/kernel-git-content/kernel-git-content.tex b/slides/kernel-git-content/kernel-git-content.tex
deleted file mode 100644
index bdcb9599..00000000
--- a/slides/kernel-git-content/kernel-git-content.tex
+++ /dev/null
@@ -1,381 +0,0 @@
-\begin{frame}
- \frametitle{What is Git?}
- \begin{itemize}
- \item A version control system, like CVS, SVN, Perforce or ClearCase
- \item Originally developed for the Linux kernel development, now
- used by a large number of projects, including U-Boot, GNOME,
- Buildroot, uClibc and many more
- \item Contrary to CVS or SVN, Git is a distributed version control
- system
- \begin{itemize}
- \item No central repository
- \item Everybody has a local repository
- \item Local branches are possible, and very important
- \item Easy exchange of code between developers
- \item Well-suited to the collaborative development model used in
- open-source projects
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Install and Setup}
- \begin{itemize}
- \item Git is available as a package in your distribution
- \begin{itemize}
- \item \code{sudo apt install git}
- \end{itemize}
- \item Everything is available through the git command
- \begin{itemize}
- \item \code{git} has many commands, called using
- \code{git <command>}, where \code{<command>} can be
- \code{clone}, \code{checkout}, \code{branch}, etc.
- \item Help can be found for a given command using
- \code{git help <command>}
- \end{itemize}
- \item Set up your name and e-mail address
- \begin{itemize}
- \item They will be referenced in each of your commits
- \item \code{git config --global user.name 'My Name'}
- \item \code{git config --global user.email me at mydomain.net}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Clone a Repository}
- \begin{itemize}
- \item To start working on a project, you use Git's clone operation.
- \item With CVS or SVN, you would have used the checkout operation,
- to get a working copy of the project (latest version)
- \item With Git, you get a full copy of the repository, including the
- history, which allows to perform most of the operations offline.
- \item Cloning Linus Torvalds' Linux kernel repository
- \code{git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git}
- \item \code{git://} is a special Git protocol. Most repositories can
- also be accessed using \code{https://}, but this is slower.
- \item After cloning, in \code{linux/}, you have the repository and a
- working copy of the master branch.
- \end{itemize}
-\end{frame}
-
-\begin{frame}[fragile]
- \frametitle{Explore the History}
- \begin{itemize}
- \item \code{git log} will list all the commits. The latest commit is
- the first.
-{\scriptsize
-\begin{verbatim}
-commit 4371ee353c3fc41aad9458b8e8e627eb508bc9a3
-Author: Florian Fainelli <florian at openwrt.org>
-Date: Mon Jun 1 02:43:17 2009 -0700
-
-MAINTAINERS: take maintainership of the cpmac Ethernet driver
-
-This patch adds me as the maintainer of the CPMAC (AR7)
-Ethernet driver.
-
-Signed-off-by: Florian Fainelli <florian at openwrt.org>
-Signed-off-by: David S. Miller <davem at davemloft.net>
-\end{verbatim}
-}
- \item \code{git log -p} will list the commits with the corresponding
- diff
- \item The history in Git is not linear like in CVS or SVN, but it is
- a graph of commits
- \begin{itemize}
- \item Makes it a little bit more complicated to understand at the
- beginning
- \item But this is what allows the powerful features of Git
- (distributed, branching, merging)
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Visualize the History: gitk}
- \begin{itemize}
- \item \code{gitk} is a graphical tool that represents the history of
- the current Git repository
- \item Can be installed from the \code{gitk} package
- \end{itemize}
- \begin{center}
- \includegraphics[height=0.65\textheight]{slides/kernel-git-content/gitk.png}
- \end{center}
-\end{frame}
-
-\begin{frame}
- \frametitle{Visualize the History: cgit}
- \begin{itemize}
- \item Another great tool is cgit, a web interface to Git. For the
- kernel sources, it is used on \url{https://git.kernel.org/}
- \end{itemize}
- \begin{center}
- \includegraphics[height=0.65\textheight]{slides/kernel-git-content/git-kernel-org.png}
- \end{center}
-\end{frame}
-
-\begin{frame}
- \frametitle{Update your Repository}
- \begin{itemize}
- \item The repository that has been cloned at the beginning will
- change over time
- \item Updating your local repository to reflect the changes of the
- remote repository will be necessary from time to time
- \item \code{git pull}
- \item Internally, does two things
- \begin{itemize}
- \item Fetch the new changes from the remote repository
- (\code{git fetch})
- \item Merge them in the current branch (\code{git merge})
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Tags}
- \begin{itemize}
- \item The list of existing tags can be found using
- \begin{itemize}
- \item \code{git tag -l}
- \end{itemize}
- \item To check out a working copy of the repository at a given tag
- \begin{itemize}
- \item \code{git checkout <tagname>}
- \end{itemize}
- \item To get the list of changes between a given tag and the latest
- available version
- \begin{itemize}
- \item \code{git log v4.19..master}
- \end{itemize}
- \item List of changes with diff on a given file between two tags
- \begin{itemize}
- \item \code{git log -p v4.18..v4.19 MAINTAINERS}
- \end{itemize}
- \item With gitk
- \begin{itemize}
- \item \code{gitk v4.19..master}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Branches}
- \begin{itemize}
- \item To start working on something, the best is to make a branch
- \begin{itemize}
- \item It is local-only, nobody except you sees the branch
- \item It is fast
- \item It allows to split your work on different topics, try
- something and throw it away
- \item It is cheap, so even if you think you're doing something
- small and quick, do a branch
- \end{itemize}
- \item Unlike other version control systems, Git encourages the use
- of branches. Don't hesitate to use them.
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Branches}
- \begin{itemize}
- \item Create a branch
- \begin{itemize}
- \item \code{git branch <branchname>}
- \end{itemize}
- \item Move to this branch
- \begin{itemize}
- \item \code{git checkout <branchname>}
- \end{itemize}
- \item Both at once (create and switch to branch)
- \begin{itemize}
- \item \code{git checkout -b <branchname>}
- \end{itemize}
- \item List of local branches
- \begin{itemize}
- \item \code{git branch}
- \end{itemize}
- \item List of all branches, including remote branches
- \begin{itemize}
- \item \code{git branch -a}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Making Changes}
- \begin{itemize}
- \item Edit a file with your favorite text editor
- \item Get the status of your working copy
- \begin{itemize}
- \item \code{git status}
- \end{itemize}
- \item Git has a feature called the index, which allows you to stage
- your commits before committing them. It allows to commit only part
- of your modifications, by file or even by chunk.
- \item On each modified file
- \begin{itemize}
- \item \code{git add <filename>}
- \end{itemize}
- \item Then commit. No need to be on-line or connected to commit
- \begin{itemize}
- \item Linux requires the -s option to sign your changes
- \item \code{git commit -s}
- \end{itemize}
- \item If all modified files should be part of the commit
- \begin{itemize}
- \item \code{git commit -as}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Sharing Changes: E-mail}
- \begin{itemize}
- \item The simplest way of sharing a few changes is to send patches
- by e-mail
- \item The first step is to generate the patches
- \begin{itemize}
- \item \code{git format-patch master..<yourbranch>}
- \item Will generate one patch for each of the commits done on
- \code{<yourbranch>}
- \item The patch files will be \code{0001-....}, \code{0002-....},
- etc.
- \end{itemize}
- \item The second step is to send these patches by e-mail
- \begin{itemize}
- \item \code{git send-email --compose --to email at domain.com 00*.patch}
- \end{itemize}
- \begin{itemize}
- \item Required Ubuntu package: \code{git-email}
- \item In a later slide, we will see how to use git config to set
- the SMTP server, port, user and password.
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Sharing Changes: Your Own Repository}
- \begin{itemize}
- \item If you do a lot of changes and want to ease collaboration with
- others, the best is to have your own public repository
- \item Use a git hosting service on the Internet:
- \begin{itemize}
- \item GitLab (\url{https://gitlab.com/})
- \begin{itemize}
- \item Open Source server. Proprietary and commercial extensions
- available.
- \end{itemize}
- \item GitHub (\url{https://github.com/})
- \begin{itemize}
- \item For public repositories. Need to pay for private
- repositories.
- \end{itemize}
- \end{itemize}
- \item Publish on your own web server
- \begin{itemize}
- \item Easy to implement.
- \item Just needs git software on the server and ssh access.
- \item Drawback: only supports http cloning (less efficient)
- \end{itemize}
- \item Set up your own git server
- \begin{itemize}
- \item Most flexible solution.
- \item Today's best solutions are \code{gitolite}
- (\url{https://github.com/sitaramc/gitolite}) for the server and
- \code{cgit} for the web interface
- (\url{https://git.zx2c4.com/cgit/about/}).
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Sharing changes: HTTP Hosting}
- \begin{itemize}
- \item Create a bare version of your repository
- \begin{itemize}
- \item \code{cd /tmp}
- \item \code{git clone --bare ~/project project.git}
- \item \code{touch project.git/git-daemon-export-ok}
- \end{itemize}
- \item Transfer the contents of \code{project.git} to a
- publicly-visible place (reachable read-only by HTTP for everybody,
- and read-write by you through SSH)
- \item Tell people to clone
- \code{https://yourhost.com/path/to/project.git}
- \item Push your changes using
- \begin{itemize}
- \item
- \code{git push ssh://yourhost.com/path/to/project.git srcbranch:destbranch}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-\begin{frame}
- \frametitle{Tracking Remote Trees}
- \begin{itemize}
- \item In addition to the official Linus Torvalds tree, you might
- want to use other development or experimental trees
- \begin{itemize}
- \item The OMAP tree at
- \code{git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git}
- \item The stable realtime tree at
- \code{git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git}
- \end{itemize}
- \item The \code{git remote} command allows to manage remote trees
- \begin{itemize}
- \item
- \code{git remote add rt git://git.kernel.org/pub/scm/ linux/kernel/git/rt/linux-stable-rt.git}
- \end{itemize}
- \item Get the contents of the tree
- \begin{itemize}
- \item \code{git fetch rt}
- \end{itemize}
- \item Switch to one of the branches
- \begin{itemize}
- \item \code{git checkout rt/master}
- \end{itemize}
- \end{itemize}
-\end{frame}
-
-
-\begin{frame}
- \frametitle{git-gui}
- \url{https://www.git-scm.com/docs/git-gui}
- \begin{itemize}
- \item A graphical interface to create and manipulate commits,
- replacing multiple git command-line commands.
- \item Not meant for history browsing (opens \code{gitk}
- when needed).
- \begin{center}
- \includegraphics[height=0.45\textheight]{slides/kernel-git-content/git-gui.png}
- \end{center}
- \item Example usage on Ubuntu/Debian:\\
- \code{sudo apt install git-gui}\\
- \code{git gui blame Makefile}
- \end{itemize}
-\end{frame}
-
-
-\begin{frame}
- \frametitle{About Git}
- We have just seen the very basic features of Git.
-
- Many more interesting features are available (rebasing,
- bisection, merging and more). For more details:
- \begin{columns}
- \column{0.6\textwidth}
- \begin{itemize}
- \item Git Manual
- \newline \url{https://schacon.github.com/git/user-manual.html}
- \item Git Book (freely available on-line, or in print form)
- \newline \url{https://git-scm.com/book}
- \item Git official website
- \newline \url{https://git-scm.com/}
- \item Video: James Bottomley's tutorial on using Git
- \newline \url{https://bit.ly/2fZJxLZ}
- \end{itemize}
- \column{0.4\textwidth}
- \includegraphics[height=0.45\textheight]{slides/kernel-git-content/progit2.png}
- \end{columns}
-\end{frame}
diff --git a/slides/kernel-git-content/progit2.png b/slides/kernel-git-content/progit2.png
deleted file mode 100644
index 2319ec05..00000000
Binary files a/slides/kernel-git-content/progit2.png and /dev/null differ
diff --git a/slides/kernel-git-lab/kernel-git-lab.tex b/slides/kernel-git-lab/kernel-git-lab.tex
deleted file mode 100644
index 0ffd944e..00000000
--- a/slides/kernel-git-lab/kernel-git-lab.tex
+++ /dev/null
@@ -1,9 +0,0 @@
-\setuplabframe
-{Going further: git}
-{
- \begin{itemize}
- \item Get familiar with git by contributing to a real project: the
- Linux kernel
- \item Send your patches to the maintainers and mailing lists.
- \end{itemize}
-}
diff --git a/slides/kernel-git-title/kernel-git-title.tex b/slides/kernel-git-title/kernel-git-title.tex
deleted file mode 100644
index 87cfa581..00000000
--- a/slides/kernel-git-title/kernel-git-title.tex
+++ /dev/null
@@ -1 +0,0 @@
-\subsection{Introduction to Git}
More information about the training-materials-updates
mailing list