Sorry Rick, no, I was asking openssl-dev. I sent the email solely to
[email protected] as recommended on the web site, and it looks like it
rewrote it 'To' you and 'Cc' to openssl-dev. Sorry for the confusion.
Regards,
jjf
On 30/11/2015 17:57, Puckett, Rick via RT wrote:
> Jeremy, > > Are you asking me? I don't have commit access to the repository.
> >
Obviously, I would endorse adding this patch as we have Sun T-3 >
systems. :-) As the patch wasn't incorporated into an official >
release, I worked around this issue by using the configure parameter >
"solaris-sparcv7". > > - Rick > > -----Original Message-----
>From: Jeremy Farrell via RT [mailto:[email protected]]
>To: Puckett, Rick (IS)
>Cc: [email protected] > > On Mon Jul 20 13:03:05 UTC 2015 Andy
Polyakov wrote: >> >>> I applied the patch you sent and
configured/compiled using >> >>> "solaris-sparcv9-gcc" and the program
completes normally. As I am >>> unable to use patched/unofficial code
for our operational ... >> >> What is criteria for being "official"?
Explicitly released as >> tar-ball >or just commit to repository? > >
Unless I'm missing it, this patch doesn't appear to have been >
committed to the repository yet. Any chance you could get this into >
1.0.2e?
--
J. J. Farrell
_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
