shaba/libxml2
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/libxml2.git synced 2025-03-09 04:58:16 +03:00
Code

Change bug tracker URL

Browse Source
This commit is contained in:
Nick Wellnhofer 2019-02-15 17:20:18 +01:00
parent 656df97d6d
commit 04fbfa3f19
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING
View File

@ -10,7 +10,7 @@ Start discussions and send patches to the mailing list, or file a bug and
add a patch as attachment.
https://mail.gnome.org/mailman/listinfo/xml
https://bugzilla.gnome.org/enter_bug.cgi?product=libxml2
https://gitlab.gnome.org/GNOME/libxml2/issues
Format patches with git-format-patch and use plain text attachments
if possible.

2
doc/site.xsl
View File

@ -406,7 +406,7 @@
<li><a href="http://sourceforge.net/projects/libxml2-pas/">Pascal bindings</a></li>
<li><a href="http://libxml.rubyforge.org/">Ruby bindings</a></li>
<li><a href="http://tclxml.sourceforge.net/">Tcl bindings</a></li>
<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Bug Tracker</a></li>
<li><a href="https://gitlab.gnome.org/GNOME/libxml2/issues">Bug Tracker</a></li>
</ul>
</xsl:variable>
<xsl:template name="toc">

8
doc/xml.html
View File

@ -526,7 +526,7 @@ xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
<p>Well, bugs or missing features are always possible, and I will make a
point of fixing them in a timely fashion. The best way to report a bug is to
use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
use the <a href="https://gitlab.gnome.org/GNOME/libxml2/issues">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>
@ -569,7 +569,7 @@ posting</span></strong>:</p>
<li>Check the <a href="http://mail.gnome.org/archives/xml/">list
archives</a> to see if the problem was reported already. In this case
there is probably a fix available, similarly check the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">registered
href="https://gitlab.gnome.org/GNOME/libxml2/issues">registered
open bugs</a>.</li>
<li>Make sure you can reproduce the bug with xmllint or one of the test
programs found in source in the distribution.</li>
@ -586,7 +586,7 @@ answer a given question, ask on the list.</p>
<p>To <span style="color: #E50000">be really clear about support</span>:</p>
<ul>
<li>Support or help <span style="color: #E50000">requests MUST be sent to
the list or on bugzilla</span> in case of problems, so that the Question
the list or the bug tracker</span> in case of problems, so that the Question
and Answers can be shared publicly. Failing to do so carries the implicit
message "I want free support but I don't want to share the benefits with
others" and is not welcome. I will automatically Carbon-Copy the
@ -617,7 +617,7 @@ it's a good starting point.</p>
<p>You can help the project in various ways, the best thing to do first is to
subscribe to the mailing-list as explained before, check the <a
href="http://mail.gnome.org/archives/xml/">archives </a>and the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome bug
href="https://gitlab.gnome.org/GNOME/libxml2/issues">Gnome bug
database</a>:</p>
<ol>
<li>Provide patches when you find problems.</li>