From 87c76bdbb6e64484959892909b9a411fe7073a59 Mon Sep 17 00:00:00 2001 From: David King Date: Sun, 19 Feb 2012 16:18:37 +0000 Subject: [PATCH] docs: Remove some old GMenu documentation --- gio/gapplication.c | 6 ++---- gio/gmenu.c | 3 --- 2 files changed, 2 insertions(+), 7 deletions(-) diff --git a/gio/gapplication.c b/gio/gapplication.c index 0db05ba..317a1aa 100644 --- a/gio/gapplication.c +++ b/gio/gapplication.c @@ -95,10 +95,8 @@ * g_action_group_activate_action() on the application, it is always * invoked in the primary instance. The actions are also exported on * the session bus, and GIO provides the #GDBusActionGroup wrapper to - * conveniently access them remotely. Additionally, g_application_set_app_menu() - * and g_application_set_menubar() can be used to export representation - * data for the actions, in the form of #GMenuModels. GIO provides - * a #GDBusMenuModel wrapper for remote access to exported #GMenuModels. + * conveniently access them remotely. GIO provides a #GDBusMenuModel wrapper + * for remote access to exported #GMenuModels. * * There is a number of different entry points into a GApplication: * diff --git a/gio/gmenu.c b/gio/gmenu.c index f924290..c80b6bf0 100644 --- a/gio/gmenu.c +++ b/gio/gmenu.c @@ -38,9 +38,6 @@ * a regular item, use g_menu_insert(). To add a section, use * g_menu_insert_section(). To add a submenu, use * g_menu_insert_submenu(). - * - * Often it is more convenient to create a #GMenu from an XML - * fragment, using GMenu Markup. */ /** -- 2.7.4