From: Michael Smith Date: Tue, 15 Jul 2008 22:53:00 +0000 (+0000) Subject: gst/: GstRegistryPool doesn't exist; don't refer to it in docs. X-Git-Tag: RELEASE-0_10_21~97 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=72e0b732f6f4a727355d7699f87442abaadcea06;p=platform%2Fupstream%2Fgstreamer.git 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 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2008-07-15 Michael Smith + + * 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 * gst/gst.c: diff --git a/gst/gstplugin.c b/gst/gstplugin.c index 63ab0e8..11fe181 100644 --- a/gst/gstplugin.c +++ b/gst/gstplugin.c @@ -36,12 +36,9 @@ * #GstPluginInitFunc function that was provided in the * gst_plugin_desc. * - * 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 --- 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. * * Design: *