On 2012-04-09 16:06, Thomas Goirand wrote:
----- Original message -----
Hi Thomas,
On 2012-04-08 17:29, Thomas Goirand wrote:
----- Original message -----
If you want to be helpful, answer the question, or better yet, fix
the text, don't just close the report.
Filipus,
ultimately, it's the maintainers decision here.
What?
It's the maintainers decision to decide the faith
of a bug report, to change severity, or to close
it if he sees fit.
What makes you think so?
Please don't do bug tracker system ping-pong
without at least providing a new text!
I'm not sure what you mean, but I can't recommend a new text. I am not
in the mind of the person who wrote this. I do not know what he meant.
I really think it's clear enough. What part you
don't understand exactly?
I already asked a question showing what I don't understand:
How would the PHP interpreter be a
configuration known to be inherently insecure?
You've been critic about
it, so I thought you could rewrite. Maybe you can
rewrite with your own words what you understand and
ask for more insights on parts you don't, so that
finally, we have something clear enough?
I already asked. But I also suggested some approaches that could fix:
The whole list is
presented as configurations known to be inherently insecure. Please
either remove those which are not about configuration, present the list
differently, or clarify your understanding of what "configuration" means.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
