From 5c12c36c585db964edd4d8f3242b24d28ae2e3b8 Mon Sep 17 00:00:00 2001
From: Damien Lespiau <damien.lespiau@intel.com>
Date: Mon, 31 Dec 2012 14:59:55 +0000
Subject: [PATCH] doc: Don't use the HTML <ul> but the DocBook equivalent

Of course, this confused gtk-doc.

(cherry picked from commit be512104784a9200a2e98a75d16a56e3897a8845)
---
 cogl/cogl-matrix-stack.h | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/cogl/cogl-matrix-stack.h b/cogl/cogl-matrix-stack.h
index 1f70bd07c..0ba81953c 100644
--- a/cogl/cogl-matrix-stack.h
+++ b/cogl/cogl-matrix-stack.h
@@ -66,13 +66,14 @@
  * Compared to using the #CoglMatrix api directly to track many
  * related transforms, these can be some advantages to using a
  * #CoglMatrixStack:
- * <ul>
- *   <li>Faster equality comparisons of transformations</li>
- *   <li>Efficient comparisons of the differences between arbitrary
- *   transformations</li>
- *   <li>Avoid redundant arithmetic related to common transforms</li>
- *   <li>Can be more space efficient (not always though)</li>
- * </ul>
+ * <itemizedlist>
+ *   <listitem>Faster equality comparisons of transformations</listitem>
+ *   <listitem>Efficient comparisons of the differences between arbitrary
+ *   transformations</listitem>
+ *   <listitem>Avoid redundant arithmetic related to common transforms
+ *   </listitem>
+ *   <listitem>Can be more space efficient (not always though)</listitem>
+ * </itemizedlist>
  *
  * For reference (to give an idea of when a #CoglMatrixStack can
  * provide a space saving) a #CoglMatrix can be expected to take 72