Re: Re: PHP 4.0 Bug #6984 Updated: problems w/ session_destroy() function
| From: | Jani Taskinen | Date: | Mon, 02 Oct 2000 20:50:20 +0000 |
| Subject: | Re: Re: PHP 4.0 Bug #6984 Updated: problems w/ session_destroy() function | ||
| References: | 1 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-34096@lists.php.net to get a copy of this message | ||
On Mon, 2 Oct 2000, André Langhorst wrote:
>sure and it was intended I marked them "duplicate", it does not help us
>a lot to crowd the bug-db with thoses duplicates if we have a bug
>containing all necessary information and we´re able to reproduce this bug.
>if we´ve a bug matching all important facts? and these duplicates are
>all on the same system, we should not keep them.
>if we keep them, it will become more and more complicated finding useful
>information in closed bugs
I agree. But making a new status 'similar to' would help, wouldn't it?
You should also remember that people who submit bug reports usually
want to have a notice that the bug has been fixed. And as it seems like
not all of the submitters always respond to feedback queries for example.
(I just got 1 feedback of 4 requests for same bug from different submitters)
And that 'similar' or 'same as' status could work like this:
When one of the bug reports is closed then ALL of the submitters of the
bugs mentioned in similar bugs field receive that closing notice..
--Jani