2012/10/3= 1 Charles Oliver Nutter <headius@headius.com>
Patrick: It would probably also be better if you made this a redmine
issue and/or pull request. Patches emailed to ruby-core tend to get
forgotten.

Thanks for pointing this= out, redmine issues are preferred since it's easier to keep track of t= hem for a longer period of time.

=A0

On Wed, Oct 31, 2012 at 9:43 AM, Charles Oliver Nutter
<headius@headius.com> wrot= e:
> We have incorporated Patrick's SNI patch for upcoming release JRub= y
> 1.7.1 and jruby-openssl 0.8.0, and are interested in seeing the test > patch get in as well. For now, we're excluding the test in questio= n
> using minitest excludes.
>
> I have also sent a few recent pull requests to add more jruby-openssl<= br> > tests to the MRI suite. We have already incorporated them into our
> fork of ruby_1_9_3 and I am standing by to help sort out issues.
>
> I know ruby-core folks are busy with feature-freeze tasks. Hopefully > after RubyConf we can circle back to these tests and get them in.
>

Thank you Charlie! Thi= ngs are settling down to normal again after RubyConf and I'm trying to = take care of as much as I can get done before 2.0.0 now. I saw the issues a= bout integrating JRuby OpenSSL tests, and I agree it's the right thing = to do. I'll run them with CRuby, see where things differ and I will pro= bably get back to you guys when it comes to sorting out these differences.= =A0

SNI is an attractive feature, the only problem that I f= ace now is that the official feature freeze is already effective. I discuss= ed this with nahi at RubyConf, it might be possible to make an exception fo= r OpenSSL, since it's an extension. So it might be possible to implemen= t new features if we consider them important! I will ask if it's possib= le in the corresponding thread.

-Martin