summaryrefslogtreecommitdiff
path: root/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
diff options
context:
space:
mode:
authorJohn Ogness <john.ogness@linutronix.de>2018-04-19 11:03:45 +0200
committerJohn Ogness <john.ogness@linutronix.de>2018-04-19 11:03:45 +0200
commitea793b23c98403cefb38670d02a778b843bdf997 (patch)
treeabef3328bd017512394c315ddff9a3bd4b40a2be /kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
parent6c4b8bc457831a351875ec1415d37ccb471bfc20 (diff)
replace *all* tabs with spaces
There are times when tabs are allowed and times when they are not. Let's just simply never use tabs for anything. This makes it easy to find presentations where tabs were accidentally inserted. Signed-off-by: John Ogness <john.ogness@linutronix.de>
Diffstat (limited to 'kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex')
-rw-r--r--kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex b/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
index ce4c69a..57f9c09 100644
--- a/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
+++ b/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
@@ -12,7 +12,7 @@
\item Verstehen, warum strikte Coding-Style-Regeln wichtig sind
\item Verstehen, warum man einen aktuellen Kernel verwenden sollte
\item Kennenlernen der Möglichkeiten und Vorteile der Zusammenarbeit
- mit der Community (Mailinglisten, IRC, Wikis...)
+ mit der Community (Mailinglisten, IRC, Wikis...)
\end{itemize}
\subsection*{Unterrichts-Ablauf}