The branch OpenSSL_1_0_2-stable has been updated via 8f486d793b2b12d4cf275eb39f4b97dade1044e3 (commit) from 706c85da79f8efb5f4da661f4a5117a8bbd4343b (commit)
- Log ----------------------------------------------------------------- commit 8f486d793b2b12d4cf275eb39f4b97dade1044e3 Author: Matt Caswell <m...@openssl.org> Date: Sun Nov 1 14:41:29 2015 +0000 Clarify the preferred way of creating patch files Clarify that git format-patch output is preferred for creating patch files. Reviewed-by: Richard Levitte <levi...@openssl.org> (cherry picked from commit f89ee71bc81017e04ac50f570d8aed87f495bcf2) ----------------------------------------------------------------------- Summary of changes: CONTRIBUTING | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index 1d46f7b..9d63d8a 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -22,8 +22,14 @@ current Git or the last snapshot. They should follow our coding style warnings using the --strict-warnings flag. OpenSSL compiles on many varied platforms: try to ensure you only use portable features. -Our preferred format for changes is "diff -u" output. One method is to use -"git diff" Another is to generate it something like this: +Our preferred format for patch files is "git format-patch" output. For example +to provide a patch file containing the last commit in your local git repository +use the following command: + +# git format-patch --stdout HEAD^ >mydiffs.patch + +Another method of creating an acceptable patch file without using git is as +follows: # cd openssl-work # [your changes] _____ openssl-commits mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits