summaryrefslogtreecommitdiff
path: root/docs/bugs.html
diff options
context:
space:
mode:
authorsangwan.kwon <sangwan.kwon@samsung.com>2016-07-28 15:17:14 +0900
committersangwan.kwon <sangwan.kwon@samsung.com>2016-07-28 15:17:14 +0900
commit1ca1a139b4c1a00de4d72f64b7411e118111a161 (patch)
tree2c93e5dbce5b42d1efd45520b1c8cd50b6bf6998 /docs/bugs.html
parentfe8ea3dba5971ab3f47090ba52d7f824c3d23545 (diff)
parentd4d35351fd63a7051a7cbef2002cb0c641925ec3 (diff)
downloadxmlsec1-1ca1a139b4c1a00de4d72f64b7411e118111a161.tar.gz
xmlsec1-1ca1a139b4c1a00de4d72f64b7411e118111a161.tar.bz2
xmlsec1-1ca1a139b4c1a00de4d72f64b7411e118111a161.zip
Merge branch 'upstream' into tizen
Change-Id: Iacc73c9ed5e9cfd188df62c405426bfa89bf4e51
Diffstat (limited to 'docs/bugs.html')
-rw-r--r--docs/bugs.html38
1 files changed, 32 insertions, 6 deletions
diff --git a/docs/bugs.html b/docs/bugs.html
index 428c0ad8..bc973704 100644
--- a/docs/bugs.html
+++ b/docs/bugs.html
@@ -2,8 +2,36 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>XML Security Library: Reporting Bugs</title>
+<style type="text/css">
+table.CALSTABLE > tbody > tr:nth-child(1) > td:nth-child(1) {
+ width: 20em;
+}
+</style>
+<style type="text/css">
+table.CALSTABLE > tbody > tr:nth-child(1) > td:nth-child(1) {
+ width: 20em;
+}
+.synopsis, .classsynopsis {
+ background: #eeeeee;
+ border: solid 1px #aaaaaa;
+}
+.programlisting {
+ background: #eeeeee;
+ border: solid 1px #000000;
+}
+.navigation {
+ background: #eeeeee;
+ border: solid 1px #000000;
+}
+.navigation a {
+ color: initial;
+}
+.navigation a:visited {
+ color: initial;
+}
+</style>
</head>
-<body><table witdh="100%" valign="top"><tr valign="top">
+<body><table width="100%" valign="top"><tr valign="top">
<td valign="top" align="left" width="210">
<img src="images/logo.gif" alt="XML Security Library" border="0"><p></p>
<ul>
@@ -47,8 +75,7 @@
<p>
Well, any big enough program has a bug. You simply don't know where
exactly :) The best way to report a bug is to use the
-<a href="http://bugzilla.gnome.org/buglist.cgi?product=xmlsec">Gnome bug
-tracking database</a>. Please, make sure to use the "xmlsec" module name.
+<a href="https://github.com/lsh123/xmlsec/issues">GitHub Issues Tracker</a>.
There is also a mailing list
<a href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a> with
<a href="http://www.aleksey.com/pipermail/xmlsec">online
@@ -87,9 +114,8 @@ Any private or confidential information posted there became public.
The author of XMLSec library assumes no responsibility for any damage caused
by any information distribution using XMLSec
<a href="http://www.aleksey.com/pipermail/xmlsec">mailing
-list</a>, GNOME CVS or
-<a href="http://bugzilla.gnome.org/buglist.cgi?product=xmlsec">Gnome bug
-tracking database</a>.
+list</a>, <a href="https://github.com/lsh123/xmlsec">GitHub Source Code</a> or
+<a href="https://github.com/lsh123/xmlsec/issues">GitHub Issue Tracker</a>.
</p>
<p>
</p>