[gmime: 1/5] Updated docs



commit 1cd31c2cd45476efc9f94f21806277abfe8a07ca
Author: Jeffrey Stedfast <jestedfa microsoft com>
Date:   Mon Mar 20 09:19:40 2017 -0400

    Updated docs

 docs/reference/resources.sgml |   29 ++++++++++++-----------------
 gmime/gmime-header.c          |    2 +-
 gmime/gmime-param.c           |    2 +-
 3 files changed, 14 insertions(+), 19 deletions(-)
---
diff --git a/docs/reference/resources.sgml b/docs/reference/resources.sgml
index 7904140..3f71f15 100644
--- a/docs/reference/resources.sgml
+++ b/docs/reference/resources.sgml
@@ -1,4 +1,4 @@
-<refentry id="gmime-resources" revision="1 Feb 2003">
+<refentry id="gmime-resources" revision="20 Mar 2017">
   <refmeta>
     <refentrytitle>Mailing lists and bug reports</refentrytitle>
     <manvolnum>3</manvolnum>
@@ -15,35 +15,30 @@ Getting help with GMime
     <para>
 If you encounter a bug, misfeature, or missing feature in GMime, please
 file a bug report at 
-<ulink url="http://bugzilla.gnome.org";>http://bugzilla.gnome.org</ulink>. 
+<ulink url="https://github.com/jstedfast/gmime/issues";>https://github.com/jstedfast/gmime/issues</ulink>. 
 We'd also appreciate reports of incomplete or misleading information in 
-the GMime documentation; file those against the &quot;docs&quot; component of the 
-&quot;gmime&quot; product in Bugzilla.
+the GMime documentation.
 </para>
     <para>
-The bug tracker should definitely be used for feature requests, it's
-not only for bugs. We track all GMime development in Bugzilla, so it's
-the way to be sure the GMime developers won't forget about an issue.
+The issue tracker should also be used for feature requests, it's not only for bugs.
+We track all GMime development in GitHub's issue tracker, so it's the way to be sure
+that the GMime developers won't forget about an issue.
 </para>
   </refsect1>
   <refsect1>
     <title>Submitting Patches</title>
     <para>
-If you develop a bugfix or enhancement for GMime, please file that in
-Bugzilla as well. Bugzilla allows you to attach files; please attach a
-patch generated by the <command>diff</command> utility, using the 
-<option>-u</option> option to make the patch more readable. All
-patches must be offered under the terms of
-the <ulink url="http://www.gnu.org/licenses/lgpl-2.1.txt";>LGPLv2.1</ulink>
+If you develop a bugfix or enhancement for GMime, please submit a pull request
+if you can. Sending the patch (as generated by a <command>diff -u</command>) to
+the mailing-list also works (although a pull request is preferred). Note that
+all patches must be offered under the terms of the
+<ulink url="http://www.gnu.org/licenses/lgpl-2.1.txt";>LGPLv2.1</ulink>
 license, so be sure you are authorized to give us the patch under
 those terms.
 </para>
     <para>
 If you want to discuss your patch before or after developing it, mail
-<ulink url="mailto:gmime-devel-list gnome org">gmime-devel-list gnome org</ulink>,
-but be sure to file
-the <ulink url="http://bugzilla.gnome.org";>Bugzilla</ulink> report as
-well, this way it's less likely to slip through the cracks.
+<ulink url="mailto:gmime-devel-list gnome org">gmime-devel-list gnome org</ulink>.
 </para>
   </refsect1>
   <refsect1>
diff --git a/gmime/gmime-header.c b/gmime/gmime-header.c
index 6c13905..f3522b5 100644
--- a/gmime/gmime-header.c
+++ b/gmime/gmime-header.c
@@ -39,7 +39,7 @@
 
 /**
  * SECTION: gmime-header
- * @title: GMimeHeader
+ * @title: GMimeHeaderList
  * @short_description: Message and MIME part headers
  * @see_also: #GMimeObject
  *
diff --git a/gmime/gmime-param.c b/gmime/gmime-param.c
index acf842a..5d2908a 100644
--- a/gmime/gmime-param.c
+++ b/gmime/gmime-param.c
@@ -50,7 +50,7 @@
 
 /**
  * SECTION: gmime-param
- * @title: GMimeParam
+ * @title: GMimeParamList
  * @short_description: Content-Type and Content-Disposition parameters
  * @see_also: #GMimeContentType
  *


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]