gst/: GstRegistryPool doesn't exist; don't refer to it in docs.

Original commit message from CVS:
* gst/gstplugin.c:
* gst/gstregistry.c:
GstRegistryPool doesn't exist; don't refer to it in docs.
Don't refer to functions that don't exist in docs, it's
unhelpful.

diff --git a/ChangeLog b/ChangeLog
index fda3d7a..22be7df 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2008-07-15  Michael Smith <msmith@songbirdnest.com>
+
+       * gst/gstplugin.c:
+       * gst/gstregistry.c:
+         GstRegistryPool doesn't exist; don't refer to it in docs.
+         Don't refer to functions that don't exist in docs, it's
+         unhelpful.
+
 2008-07-12  Sebastian Dröge  <sebastian.droege@collabora.co.uk>
 
        * gst/gst.c:

diff --git a/gst/gstplugin.c b/gst/gstplugin.c
index 63ab0e8..11fe181 100644 (file)
--- a/gst/gstplugin.c
+++ b/gst/gstplugin.c
@@ -36,12 +36,9 @@
  * #GstPluginInitFunc function that was provided in the
  * <symbol>gst_plugin_desc</symbol>.
  *
- * Once you have a handle to a #GstPlugin (e.g. from the #GstRegistryPool), you
+ * Once you have a handle to a #GstPlugin (e.g. from the #GstRegistry), you
  * can add any object that subclasses #GstPluginFeature.
  *
- * Use gst_plugin_find_feature() and gst_plugin_get_feature_list() to find
- * features in a plugin.
- *
  * Usually plugins are always automaticlly loaded so you don't need to call
  * gst_plugin_load() explicitly to bring it into memory. There are options to
  * statically link plugins to an app or even use GStreamer without a plugin

diff --git a/gst/gstregistry.c b/gst/gstregistry.c
index 0457036..1c1d27a 100644 (file)
--- a/gst/gstregistry.c
+++ b/gst/gstregistry.c
@@ -27,7 +27,6 @@
  * @see_also: #GstPlugin, #GstPluginFeature
  *
  * One registry holds the metadata of a set of plugins.
- * All registries build the #GstRegistryPool.
  *
  * <emphasis role="bold">Design:</emphasis>
  *