Hey Stan,
You accidentally sent your mail to libssh2-devel-owner@ instead of just
libssh2-devel@, which made it end up with the mailing list owners only. I'm
now forwarding it to the proper list address, lets keep it on the list now!
See below for the full content.
To answer your question in there: yes we are interested in extending our
portability to the IBM iSeries. At least if the changes are clean and
managable to review. (I'll admit that EBCDIC handling scares me a bit.)
I think you could start with rebasing your work on top of what we have in git
right now so that we have an up-to-date version of your work to start working
with to hopefully merge.
-- / daniel.haxx.se ---------- Forwarded message ---------- Date: Thu, 19 Nov 2015 15:30:40 From: Stan Prichard <SPrichard_at_liaison.com> To: "libssh2-devel-owner_at_cool.haxx.se" <libssh2-devel-owner_at_cool.haxx.se> Subject: IBM iSeries port of LIBSSH2 Hello, I am Stan Prichard, a developer at Liaison Technologies. A couple of years ago, I ported LIBSSH2 v1.2.7 to the IBM iSeries, an EBCDIC based system. These changes would also be usable on IBM zSeries systems. Additionally, I created the server-side interfaces (server KEX, message handling, etc.) to allow LIBSSH2 to be used in our SFTP Server. I have recently been given the approval to discuss these changes with you. I would like to know if you would be interested in incorporating any of these modifications into your code base. I would also like to know what licensing model is being used by your organization. Please respond if there is any interest in this proposal. Best regards, Stan Prichard Sr. Engineer, IBM(tm) Systems Liaison Technologies 3157 Royal Drive | Suite 200 | Alpharetta, GA 30022 T: +1 940.498.9625 | M: +1 214.437.3496 www.liaison.com<http://www.liaison.com/> Connect with us!<http://liaison.com/about-liaison/communities> _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-develReceived on 2015-11-19