summaryrefslogtreecommitdiff
path: root/doc/bugs.html
diff options
context:
space:
mode:
authorDaniel Veillard <veillard@redhat.com>2017-09-04 15:38:47 +0200
committerDaniel Veillard <veillard@redhat.com>2017-09-04 15:38:47 +0200
commit2960178fe8f9fe690b7f8c1c49093ff54bb56934 (patch)
treec44e5539eb495f9190316dcc2f7dfa328a985705 /doc/bugs.html
parent69936b129fedcda3514fee1a0d6b39521923cbac (diff)
downloadlibxml2-2960178fe8f9fe690b7f8c1c49093ff54bb56934.tar.gz
Release of libxml2-2.9.5v2.9.5
* configure.ac, doc/xslt.html: updated for the release * doc/*, python/setup.py, testapi.c: regenerated
Diffstat (limited to 'doc/bugs.html')
-rw-r--r--doc/bugs.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs.html b/doc/bugs.html
index 55ff296a..52970d3b 100644
--- a/doc/bugs.html
+++ b/doc/bugs.html
@@ -13,7 +13,7 @@ use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
bug tracking database</a> (make sure to use the "libxml2" module name). I
look at reports there regularly and it's good to have a reminder when a bug
is still open. Be sure to specify that the bug is for the package libxml2.</p><p>For small problems you can try to get help on IRC, the #xml channel on
-irc.gnome.org (port 6667) usually have a few person subscribed which may help
+irc.gnome.org (port 6667) usually has a few people subscribed which may help
(but there is no guarantee and if a real issue is raised it should go on the
mailing-list for archival).</p><p>There is also a mailing-list <a href="mailto:xml@gnome.org">xml@gnome.org</a> for libxml, with an <a href="http://mail.gnome.org/archives/xml/">on-line archive</a> (<a href="http://xmlsoft.org/messages">old</a>). To subscribe to this list,
please visit the <a href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and