X-Git-Url: http://wagnertech.de/git?a=blobdiff_plain;f=i686-linux-gnu-4.7%2Fusr%2Fshare%2Fdoc%2Flibpplv4-13%2FBUGS;fp=i686-linux-gnu-4.7%2Fusr%2Fshare%2Fdoc%2Flibpplv4-13%2FBUGS;h=340a7ba4cb7aa3a8abf79a2ff6b5ca1597c0232b;hb=94df942c2c7bd3457276fe5b7367623cbb8c1302;hp=0000000000000000000000000000000000000000;hpb=4dd7d9155a920895ff7b1cb6b9c9c676aa62000a;p=cross.git

diff --git a/i686-linux-gnu-4.7/usr/share/doc/libpplv4-13/BUGS b/i686-linux-gnu-4.7/usr/share/doc/libpplv4-13/BUGS
new file mode 100644
index 0000000..340a7ba
--- /dev/null
+++ b/i686-linux-gnu-4.7/usr/share/doc/libpplv4-13/BUGS
@@ -0,0 +1,22 @@
+
+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
+the reported misbehavior is the best thing you can do to help us fix
+the library.  Of course, this is not always possible and we will
+welcome any kind of bug report.  Anyway, you may be interested to read
+http://www.chiark.greenend.org.uk/~sgtatham/bugs.html on how to report
+bugs effectively.
+
+
+KNOWN BUGS
+==========
+
+All known bugs were resolved before the release.  It is likely that
+there are still bugs in the released version.  Any bugs found after
+the release will be listed at http://bugseng.com/products/ppl/Bugs/ .