Date: 09/25/00
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #6876 Updated: Error when using Make after successful ./configure ......"
- Previous message: Jason Greene: "[PHP-DEV] best way to submit patches"
- In reply to: Bug Database: "[PHP-DEV] PHP 4.0 Bug #3075 Updated: inconsistency in checking include_path"
- Next in thread: Bug Database: "[PHP-DEV] PHP 4.0 Bug #3075 Updated: inconsistency in checking include_path"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
BD>> Why don't the PHP developers check for themselves whether the
BD>> problem is still there? I'm tired of having to report PHP bugs
Variants:
1. They are lazy.
2. They have more bugs to fix, so they don't have time to check.
2. They don't have access to your system, so they cannot be sure it fixes
bug for you.
Choose one you like the most.
BD>> 2 or 3 times because the developers wait 8 months before dealing
BD>> with them.
You can do it faster? Apply for CVS access and fix it yourself. You can
even skip the fursther and just send the patch. If it's good it will be in
in matter of days.
-- Stanislav Malyshev stas <email protected> http://www.zend.com/ +972-3-6139665 ext.106-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #6876 Updated: Error when using Make after successful ./configure ......"
- Previous message: Jason Greene: "[PHP-DEV] best way to submit patches"
- In reply to: Bug Database: "[PHP-DEV] PHP 4.0 Bug #3075 Updated: inconsistency in checking include_path"
- Next in thread: Bug Database: "[PHP-DEV] PHP 4.0 Bug #3075 Updated: inconsistency in checking include_path"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

