Code reformatting

Code Reformatting

In 2015, all the OpenSSL code was reformatted, in all release branches.

As a result the code is consistent and, to almost everyone, easier to read.

Coding Style Policy

Matt wrote a couple of blog entries about the reformatting: [[1]] and [[2]].

If you have a smaller number of local patches, you might find this recipe useful to upgrade:

• Take the original release you are currently using. Reformat it according to the second blog entry. Don't worry too much about minor failures or inconsistencies. Save that.

• Take your patched release. Reformat it according to the second blog entry. Don't worry too much about minor failures or inconsistencies. Save that.

• Run a diff between the two releases. You should, for the most part, have just your patches, reformatted.