From 6566f746f615673b2a6eeaf44d3e9c4373900c5a Mon Sep 17 00:00:00 2001
From: Matthias Clasen <mclasen@redhat.com>
Date: Sat, 1 Feb 2014 20:41:47 -0500
Subject: [PATCH] Drop use of xinclude in GTestDBus docs

---
 gio/gtestdbus.c | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/gio/gtestdbus.c b/gio/gtestdbus.c
index 53b958d8f..9d784b7c2 100644
--- a/gio/gtestdbus.c
+++ b/gio/gtestdbus.c
@@ -360,13 +360,9 @@ _g_test_watcher_remove_pid (GPid pid)
  *     Once you have a service definition file which is local to your source tree,
  * you can proceed to set up a GTest fixture using the #GTestDBus scaffolding.
  *
- * Here is an example of a test fixture for D-Bus services:
- * <programlisting>
- * <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text" href="../../../../gio/tests/gdbus-test-fixture.c">
- * <xi:fallback>FIXME: MISSING XINCLUDE CONTENT</xi:fallback>
- * </xi:include>
- * </programlisting>
- * 
+ * An example of a test fixture for D-Bus services can be found
+ * here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/tests/gdbus-test-fixture.c">gdbus-test-fixture.c</ulink>
+ *
  * Note that these examples only deal with isolating the D-Bus aspect of your
  * service. To successfully run isolated unit tests on your service you may need
  * some additional modifications to your test case fixture. For example; if your