Dear Mr BuildSmart
BuildSmart wrote:
SInce I didn't consider it a bug but rather a minor error of importance,
just out of curiosity: how do you define "bug" if not as "any error"?
I thought it would best be handled by making the maintainers aware of
the issue since the fix is relatively simple and provided to avoid the
filing of bug reports which would have occurred.
this is wrong in several ways:
- your original posting did not include the actual fix but
only what should change in the generated configure file
the actual fix was only in your mail of 12:10 today.
giving you the benefit of the doubt i'd assume for now
that it was attached to the original message, too, but
got stripped, this would not have happened with a bug
report though
- the bug database is not only a todo list, it is also
a repository of bugs fixed in the past. e.g. have you
noticed the duplicate detection when filing a bug?
with a bug fixed out of band without involving the
bugs db duplicate detection can't kick in on new bug
reports
- changelog entries usually refer to a bug number,
having them point to a mail archive instead would
be inconsistant and so bad
- same for commit messages ... add to this that it is
easy to refer to a bug number but way less so to
refer to a distinct email
So working around the bug system is not a shortcut,
it actually generates *more* work in the long run.
The bug system is there to be *used*, not to be
circumvented.
If you had submitted your finding as a bug report
with proper how-to-reproduce instructions (which
your original message did not have, what you wrote
there was way to vague) and also with your patch
to ext/standard/config.m4 things would probably
been handled just fine already. Look what mess you
caused instead ... :(
--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:
http://www.mysql.com/products/enterprise/whats_new.html
Hauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
