1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
5 <title>Mailing lists and bug reports</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7 <link rel="home" href="index.html" title="GMime 2.6 Reference Manual">
8 <link rel="up" href="gmime.html" title="Part I. GMime Overview">
9 <link rel="prev" href="gmime-changes-2-6.html" title="Changes from 2.4 to 2.6">
10 <link rel="next" href="gmime-question-index.html" title="Frequently Asked Questions">
11 <meta name="generator" content="GTK-Doc V1.18 (XML mode)">
12 <link rel="stylesheet" href="style.css" type="text/css">
14 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
15 <table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
16 <td><a accesskey="p" href="gmime-changes-2-6.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
17 <td><a accesskey="u" href="gmime.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
18 <td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
19 <th width="100%" align="center">GMime 2.6 Reference Manual</th>
20 <td><a accesskey="n" href="gmime-question-index.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
22 <div class="refentry">
23 <a name="gmime-resources"></a><div class="titlepage"></div>
24 <div class="refnamediv"><table width="100%"><tr>
26 <h2><span class="refentrytitle">Mailing lists and bug reports</span></h2>
27 <p>Mailing lists and bug reports —
28 Getting help with GMime
31 <td valign="top" align="right"></td>
33 <div class="refsect1">
34 <a name="idp5158880"></a><h2>Filing a bug report or feature request</h2>
36 If you encounter a bug, misfeature, or missing feature in GMime, please
38 <a class="ulink" href="http://bugzilla.gnome.org" target="_top">http://bugzilla.gnome.org</a>.
39 We'd also appreciate reports of incomplete or misleading information in
40 the GMime documentation; file those against the "docs" component of the
41 "gmime" product in Bugzilla.
44 The bug tracker should definitely be used for feature requests, it's
45 not only for bugs. We track all GMime development in Bugzilla, so it's
46 the way to be sure the GMime developers won't forget about an issue.
49 <div class="refsect1">
50 <a name="idp5161792"></a><h2>Submitting Patches</h2>
52 If you develop a bugfix or enhancement for GMime, please file that in
53 Bugzilla as well. Bugzilla allows you to attach files; please attach a
54 patch generated by the <span class="command"><strong>diff</strong></span> utility, using the
55 <code class="option">-u</code> option to make the patch more readable. All
56 patches must be offered under the terms of
57 the <a class="ulink" href="http://www.gnu.org/licenses/lgpl-2.1.txt" target="_top">LGPLv2.1</a>
58 license, so be sure you are authorized to give us the patch under
62 If you want to discuss your patch before or after developing it, mail
63 <a class="ulink" href="mailto:gmime-devel-list@gnome.org" target="_top">gmime-devel-list@gnome.org</a>,
65 the <a class="ulink" href="http://bugzilla.gnome.org" target="_top">Bugzilla</a> report as
66 well, this way it's less likely to slip through the cracks.
69 <div class="refsect1">
70 <a name="idp5209360"></a><h2>Mailing lists</h2>
71 <p>There is currently only one mailing-list devoted to GMime
72 itself which is for both the development of and development with
73 GMime. You can subscribe to this list
74 at <a class="ulink" href="http://mail.gnome.org/mailman/listinfo/gmime-devel-list" target="_top">http://mail.gnome.org/mailman/listinfo/gmime-devel-list</a>.
80 Generated by GTK-Doc V1.18</div>