[elinks-web patch 2/2] The elinks-bugs mailing list is out of order.

The elinks-bugs mailing list is out of order.

---
commit d525268fed3208c8432d409a28a136c9baf97884
tree 2a0a4a4d4baf25cfe423186f58868e26584d7094
parent ccebedf2f56986a5e6f282fca90eca03722a92bc
author Kalle Olavi Niemitalo <[email protected]> Sat, 21 Oct 2006 14:38:17 +0300
committer Kalle Olavi Niemitalo <[email protected]> Sat, 21 Oct 2006 14:38:17 +0300

 community.html |   23 ++++++++++++-----------
 community.txt  |   15 +++++++++++++++
 2 files changed, 27 insertions(+), 11 deletions(-)

diff --git a/community.html b/community.html
index 7c24370..97c13a3 100644
--- a/community.html
+++ b/community.html
@@ -69,18 +69,19 @@ elinks-dev
         <a href="http://linuxfromscratch.org/pipermail/elinks-dev/">archive</a> ]
 </dd>
 <dt>
-elinks-bugs
+elinks-bugs (out of order)
 </dt>
 <dd>
-        If you want to keep up to date with changes in
-        <a href="http://bugzilla.elinks.or.cz">the bug tracking system</a> via mail
-        notifications consider subscribing to this list.  Note that updates
-        relevant to a reported bug are automatically sent to the bug reporter
-        and anyone who CCs herself to it via the web interface.<br />
-        <strong>Subscribing:</strong> Simply mail to
-        <a href="mailto:[email protected]">[email protected]</a>
-        (subject or content of the mail doesn't matter) and follow the
-        instructions in the reply.
+        There used to be a mailing list to which
+        <a href="http://bugzilla.elinks.or.cz">the bug tracking system</a>
+        sent notifications whenever a bug report was changed.
+        However, this list is not currently working: you cannot
+        subscribe, and subscribers do not get messages.<br />
+        If you are interested in a bug that has already been reported,
+        you can instead add yourself to the CC list of the bug via
+        the web interface.  (If you reported the bug or voted for it,
+        then the bug tracker already notifies you about changes,
+        unless you have disabled this in your user preferences.)
 </dd>
 </dl>
 <div class="admonitionblock">
@@ -134,7 +135,7 @@ to catch someone around midnight than du
         </span>
 </div>
 <p class="validate">
-        Last Modified: 21-Oct-2006 14:26:07 EEST.
+        Last Modified: 21-Oct-2006 14:34:55 EEST.
         Validate:
         <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a>
         <a href="http://validator.w3.org/check/referer">XHTML</a>.
diff --git a/community.txt b/community.txt
index 84497a7..cc88326 100644
--- a/community.txt
+++ b/community.txt
@@ -47,6 +47,20 @@ elinks-cvs::
 	in the reply.
 ///////////////////////////////////////////////////////////////////////////////
 
+elinks-bugs (out of order)::
+
+	There used to be a mailing list to which
+	link:http://bugzilla.elinks.or.cz[the bug tracking system]
+	sent notifications whenever a bug report was changed.
+	However, this list is not currently working: you cannot
+	subscribe, and subscribers do not get messages. +
+	If you are interested in a bug that has already been reported,
+	you can instead add yourself to the CC list of the bug via
+	the web interface.  (If you reported the bug or voted for it,
+	then the bug tracker already notifies you about changes,
+	unless you have disabled this in your user preferences.)
+
+///////////////////////////////////////////////////////////////////////////////
 elinks-bugs::
 
 	If you want to keep up to date with changes in
@@ -58,6 +72,7 @@ elinks-bugs::
 	link:mailto:[email protected][[email protected]]
 	(subject or content of the mail doesn't matter) and follow the
 	instructions in the reply.
+///////////////////////////////////////////////////////////////////////////////
 
 
 NOTE: Due to spam (and bad spamfilters) we have been forced to hold back mails

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFOg7pHm9IGt60eMgRAh6VAJsGAg3EM7G1uI9dziDpvQNTi8x/QACgzhWt
whuxH1toPdoVpR/NwmXEd7E=
=VvZ/
-----END PGP SIGNATURE-----