diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index 00652f0a7f34b670cf7a8c64f8a4a197f33bfaef..4e23393f07ed583b5e588800d71ff7c0edafc2c3 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -1548,6 +1548,16 @@ here as well.  However, there are three additional requirements.
 
 \subsection{The Simpler Parts of GPLv2~\S2}
 
+% FIXME: GPLv2~\S2(a) isn't discussed heavily here and more should be
+% discussed about it.  There have been developer questions.  One idea I had
+% was to write up:
+%        http://ebb.org/bkuhn/blog/2011/03/11/linux-red-hat-gpl.html
+% as a compliance case study specific to GPLv2 Section 2(a)
+%
+% Another point to discuss here -- or maybe it goes better in the compliance
+% case study ? -- is to explain that git logs ARE adequate but possibly
+% overkill.
+
 The first (GPLv2~\S2(a)) requires that modified files carry ``prominent
 notices'' explaining what changes were made and the date of such
 changes. This section does not prescribe some specific way of