I maintain a few private branches of the OpenSSL source code, including some custom patches and changes. To keep up with things and stay up to date I review the changes at least every release, and semi-regularly try to keep up with what's in change control. I'm actually looking forward to the change; although it will mean a one-time reformat I don't think it'll be a big inconvenience. And once it's done I think it'll make the future changes easier to read.
Thanks for doing it! ________________________________________ From: openssl-dev [[email protected]] on behalf of Salz, Rich [[email protected]] Sent: 13 January 2015 14:04 To: [email protected] Subject: Re: [openssl-dev] OpenSSL coding style published > One concern I have is that I, and no doubt others, look through the diffs > between OpenSSL releases to see what the ramifications of changes are. We appreciate the issue. At a minimum, there will be pre- and post-indent tags. And the script we use to do the indentation is available (and will be in the release) so that people with modified versions can "play along at home" as it were. We had a great deal of discussion about this, and it's not something we're doing casually. We think it's the best way to move forward, even though some folks will be inconvenienced. /r$ _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
