questions: Add section-level epigraphs

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

7 files changed, 23 insertions, 0 deletions

diff --git a/appendix/questions/after.tex b/appendix/questions/after.tex
index 9715fa61..c165eb0e 100644
--- a/appendix/questions/after.tex
+++ b/appendix/questions/after.tex
@@ -4,6 +4,10 @@
 
 \section{What Does ``After'' Mean?}
 \label{sec:app:questions:What Does ``After'' Mean?}
+%
+\epigraph{There is no future.
+	  There is no past.}
+	 {Alan Moore}
 
 ``After'' is an intuitive, but surprisingly difficult concept.
 An important non-intuitive issue is that code can be delayed at
diff --git a/appendix/questions/buggy.tex b/appendix/questions/buggy.tex
index 03e47002..440682ad 100644
--- a/appendix/questions/buggy.tex
+++ b/appendix/questions/buggy.tex
@@ -4,6 +4,9 @@
 
 \section{Why Is Software Buggy?}
 \label{sec:app:questions:Why Is Software Buggy?}
+%
+\epigraph{There is no perfection, only beautiful versions of brokenness.}
+	 {Shannon L. Alder}
 
 The short answer is ``because it was written by humans, and to err
 is human''.
diff --git a/appendix/questions/concurrentparallel.tex b/appendix/questions/concurrentparallel.tex
index 016acab2..4142420e 100644
--- a/appendix/questions/concurrentparallel.tex
+++ b/appendix/questions/concurrentparallel.tex
@@ -4,6 +4,9 @@
 
 \section{What is the Difference Between ``Concurrent'' and ``Parallel''?}
 \label{sec:app:questions:What is the Difference Between ``Concurrent'' and ``Parallel''?}
+%
+\epigraph{If you cannot make a difference, make a distinction!}
+	 {Unknown}
 
 From a classic computing perspective, ``\IX{concurrent}'' and ``\IX{parallel}''
 are clearly synonyms.
diff --git a/appendix/questions/ordering.tex b/appendix/questions/ordering.tex
index 5cf6fd5a..ced9ebb7 100644
--- a/appendix/questions/ordering.tex
+++ b/appendix/questions/ordering.tex
@@ -4,6 +4,9 @@
 
 \section{How Much Ordering Is Needed?}
 \label{sec:app:questions:How Much Ordering Is Needed?}
+%
+\epigraph{A lost inch of gold may be found, a lost inch of time, never.}
+	 {Chinese proverb}
 
 Perhaps you have carefully constructed a strongly ordered concurrent
 system, only to find that it neither performs nor scales well.
diff --git a/appendix/questions/parallelfaster.tex b/appendix/questions/parallelfaster.tex
index 530cb0ae..fed33aa7 100644
--- a/appendix/questions/parallelfaster.tex
+++ b/appendix/questions/parallelfaster.tex
@@ -4,6 +4,9 @@
 
 \section{Why Aren't Parallel Programs Always Faster?}
 \label{sec:app:questions:Why Aren't Parallel Programs Always Faster?}
+%
+\epigraph{There is nothing quite so complicated as simplicity.}
+	 {Charles Poore}
 
 The short answer is ``because parallel execution often requires
 communication, and communication is not free''.
diff --git a/appendix/questions/removelocking.tex b/appendix/questions/removelocking.tex
index f713dabf..3fbcbe0b 100644
--- a/appendix/questions/removelocking.tex
+++ b/appendix/questions/removelocking.tex
@@ -4,6 +4,10 @@
 
 \section{Why Not Remove Locking?}
 \label{sec:app:questions:Why Not Remove Locking?}
+%
+\epigraph{A great number of people think they are thinking when they
+	  are merely rearranging their prejudices.}
+	 {William James}
 
 There can be no doubt that many have cast locking as the evil villain
 of parallel programming, and not entirely without reason.
diff --git a/appendix/questions/time.tex b/appendix/questions/time.tex
index 0292b08d..a4ce11ed 100644
--- a/appendix/questions/time.tex
+++ b/appendix/questions/time.tex
@@ -4,6 +4,9 @@
 
 \section{What Time Is It?}
 \label{sec:app:questions:What Time Is It?}
+%
+\epigraph{Time is a game played beautifully by children.}
+	 {Heraclitus}
 
 \begin{figure}
 \centering