[PPL-devel] [GIT] ppl/ppl(master): Using the bug tracking system is now the recommended way to report PPL issues .

[Roberto Bagnara]

Module: ppl/ppl
Branch: master
Commit: 0bfb384588dbbeb770a45f4d850514a1d87349be
URL:    http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=0bfb384588dbbeb770a45f4d850514a1d87349be

Author: Roberto Bagnara <bagnara at cs.unipr.it>
Date:   Sat Jun 13 08:50:03 2009 +0200

Using the bug tracking system is now the recommended way to report PPL issues.

---

 BUGS |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/BUGS b/BUGS
index 794468e..87627ce 100644
--- a/BUGS
+++ b/BUGS
@@ -1,9 +1,9 @@
 
-The PPL developers encourage you to report any bugs you find to
-ppl-devel at cs.unipr.it.  Here `bug' should be interpreted in its
-broadest sense: outright software errors, misfeatures, bad interfaces,
-missing or unclear documentation... whatever is a subject for possible
-improvement.
+The PPL developers encourage you to report any bugs you find using the
+bug tracking system available at https://www.cs.unipr.it/mantis/ .
+Here `bug' should be interpreted in its broadest sense: outright
+software errors, misfeatures, bad interfaces, missing or unclear
+documentation... whatever is a subject for possible improvement.
 
 As far as software bugs are concerned, the best reports are those that
 are reproducible.  Including (or pointing us to) code that exhibits