> So, whatever we call the next one, the string version must come after > "0.9.2b" (intuitively) and the hex version must be > 0x0922. Name the next "major" release 1.0 with hex code 0x010000, then go on with 1.1 == 0x010100, etc., and all of a sudden the problem is vanished. Right? ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
- Re: cvs commit: openssl-web/source index.current Ulf M�ller
- Re: cvs commit: openssl-web/source index.current Ben Laurie
- Re: cvs commit: openssl-web/source index.current Ulf M�ller
- Re: cvs commit: openssl-web/source index.current Ralf S. Engelschall
