CONTRIBUTING revision 291721
1HOW TO CONTRIBUTE TO OpenSSL 2---------------------------- 3 4Development is coordinated on the openssl-dev mailing list (see 5http://www.openssl.org for information on subscribing). If you 6would like to submit a patch, send it to rt@openssl.org with 7the string "[PATCH]" in the subject. Please be sure to include a 8textual explanation of what your patch does. 9 10You can also make GitHub pull requests. If you do this, please also send 11mail to rt@openssl.org with a brief description and a link to the PR so 12that we can more easily keep track of it. 13 14If you are unsure as to whether a feature will be useful for the general 15OpenSSL community please discuss it on the openssl-dev mailing list first. 16Someone may be already working on the same thing or there may be a good 17reason as to why that feature isn't implemented. 18 19Patches should be as up to date as possible, preferably relative to the 20current Git or the last snapshot. They should follow our coding style 21(see https://www.openssl.org/policies/codingstyle.html) and compile without 22warnings using the --strict-warnings flag. OpenSSL compiles on many varied 23platforms: try to ensure you only use portable features. 24 25Our preferred format for patch files is "git format-patch" output. For example 26to provide a patch file containing the last commit in your local git repository 27use the following command: 28 29# git format-patch --stdout HEAD^ >mydiffs.patch 30 31Another method of creating an acceptable patch file without using git is as 32follows: 33 34# cd openssl-work 35# [your changes] 36# ./Configure dist; make clean 37# cd .. 38# diff -ur openssl-orig openssl-work > mydiffs.patch 39