gst/gstplugin.c: Fix docs that mention 'plugin_desc' instead of 'gst_plugin_desc'.

Original commit message from CVS:
* gst/gstplugin.c:
Fix docs that mention 'plugin_desc' instead of 'gst_plugin_desc'.
Spotted by Josep Torra Valles <josep@fluendo.com>.

diff --git a/ChangeLog b/ChangeLog
index d14bbcf..312f817 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2007-10-03  Stefan Kost  <ensonic@users.sf.net>
+
+       * gst/gstplugin.c:
+         Fix docs that mention 'plugin_desc' instead of 'gst_plugin_desc'.
+         Spotted by Josep Torra Valles <josep@fluendo.com>.
+
 2007-10-03  Tim-Philipp Müller  <tim at centricular dot net>
 
        * gst/gstclock.h:

diff --git a/gst/gstplugin.c b/gst/gstplugin.c
index c11faeb..a0d25b0 100644 (file)
--- a/gst/gstplugin.c
+++ b/gst/gstplugin.c
@@ -29,11 +29,12 @@
  * A plugin system can provide one or more of the basic
  * <application>GStreamer</application> #GstPluginFeature subclasses.
  *
- * A plugin should export a symbol <symbol>plugin_desc</symbol> that is a
+ * A plugin should export a symbol <symbol>gst_plugin_desc</symbol> that is a
  * struct of type #GstPluginDesc.
  * the plugin loader will check the version of the core library the plugin was
  * linked against and will create a new #GstPlugin. It will then call the
- * #GstPluginInitFunc function that was provided in the plugin_desc.
+ * #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
  * can add any object that subclasses #GstPluginFeature.