summaryrefslogtreecommitdiffstats
path: root/doc/trouble.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/trouble.html')
-rw-r--r--doc/trouble.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/trouble.html b/doc/trouble.html
index c3f5576..5e8a24e 100644
--- a/doc/trouble.html
+++ b/doc/trouble.html
@@ -116,14 +116,14 @@ The PyKDE sources are mostly "sip" files which describe the interface to KDE's C
to the sip code generator. These files should be error free. If a sip or code generation error occurs,
please report it to the PyKDE mailing list at <A HREF="mailto:PyKDE@mats.imk.fraunhofer.de">
PyKDE@mats.imk.fraunhofer.de </A> Subscribe to the list
-<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pykde">here</a>
+<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pytde">here</a>
</dd>
<dt>Compile errors</dt>
<dd>
PyKDE should not experience any compile errors. Currently sip 4.0 based compiles will
generate a number of warnings - these can be safely ignored. If errors occur, please report them
to the PyKDE mailing list at <A HREF="mailto:PyKDE@mats.imk.fraunhofer.de"> PyKDE@mats.imk.fraunhofer.de </A>.
-Subscribe to the list <a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pykde">here</a>
+Subscribe to the list <a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pytde">here</a>
</dd>
</dl>
<h2>Compile-time errors</h2>
@@ -182,7 +182,7 @@ If you can locate the sip file for the class, you can comment out ("//") the mis
report it on the PyKDE mailing list at <A HREF="mailto:PyKDE@mats.imk.fraunhofer.de">
PyKDE@mats.imk.fraunhofer.de </A>. Subscribe to the list
</p>
-<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pykde">here</a>
+<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pytde">here</a>
</dd>
<dt>Other run-time errors</dt>
<dd>
@@ -193,7 +193,7 @@ because it's running from Python and not C++. If you suspect an error, please do
code and review the PyKDE docs to be sure the argument lists and expected return types are what you
thought they were. If the problem persists, report it to the PyKDE mailing list at
<A HREF="mailto:PyKDE@mats.imk.fraunhofer.de"> PyKDE@mats.imk.fraunhofer.de </A>. Subscribe to the list
-<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pykde">here</a>. <b>When reporting errors to the
+<a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pytde">here</a>. <b>When reporting errors to the
list, it's always helpful if you provide:</b>
<ul>
<li>