Dear 'The Doctor', I am not on the OpenSSL team so I'm just speaking for myself here. But I have done work on many other open-source products, so I'm responding based on my overall experience with open-source development.
When you find a problem in an open-source product, the accepted protocol is to boil the problem down to the smallest reproducible test case that reliably demonstrates the failure and then post just that information. Posting the entire output of the build procedure is incredibly lame and completely unhelpful. Posting to two different OpenSSL mailing lists is also clueless; they have different purposes. If I were a member of the OpenSSL team, I'd ignore your postings until you took the time to learn how to add value to the process instead of being a drag on other people's productivity. I also think that posting under a pseudonym is childish but maybe that's just me. PG ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
