>I think that was what started the discussion... panhenryk posted it to the >mailing list on Monday (subject - wildcard preceding term solution), and >then (I'm assuming this is the same person but it may not be) >[EMAIL PROTECTED] submitted this bug report about it with his changes >attached. Both posts asked someone else to verify that his changes didn't >break something else not obvious to him.
Moving up a level... This is one of the big challenges facing open-source projects. The code is out there, so people change it to suit their needs -- which is great. Then they want to submit those changes back to the project. Sometimes this is great -- but sometimes its not. People very rarely stop to think "Is this change good for the majority of users?" People are very quick to assume that all the other users are a lot like them. And they don't even realize they're making this assumption. In other words, just because a change CAN be made easily, doesn't mean that its a good idea. The discussion of whether its a good idea should ALWAYS precede any attempt to submit the change. -- Brian Goetz Quiotix Corporation [EMAIL PROTECTED] Tel: 650-843-1300 Fax: 650-324-8032 http://www.quiotix.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>