Idea: we might want to have a file called PROBLEMS or somesuch, in which we enumerate known problems like this one. That would communicate two things to the users: 1) that we know about the problem and possibly that we're working on it, and 2) what changes to expect as a result of this. The latter will allow them to prepare for things that would otherwise become a surprise (because they won't read the right section in CHANGES, or because they won't realise the effect the change has). Thoughts? If we god for this, it should be present in time for the release. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10 Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Software Engineer, Celo Communications: http://www.celocom.com/ Unsolicited commercial email is subject to an archival fee of $400. See <http://www.stacken.kth.se/~levitte/mail/> for more info. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: BIO_ctrl() defaule return value...
Richard Levitte - VMS Whacker Sun, 17 Sep 2000 12:22:31 -0700
- BIO_ctrl() defaule return value... Richard Levitte - VMS Whacker
- Re: BIO_ctrl() defaule return value... Richard Levitte - VMS Whacker
- Re: BIO_ctrl() defaule return value... Dr S N Henson