Re: [openssl-dev] How to contribute patches has changed

2016-05-11 Thread Joey Yandle
If it's a feature, wait until after 1.1 and then rebase. If it's a bug or doc fix or similar, please update now and ping. It's the windows RNG fix/cleanup. Just updated and now no conflicts on PR. https://github.com/openssl/openssl/pull/512 Thanks! Joey -- openssl-dev mailing list To un

Re: [openssl-dev] How to contribute patches has changed

2016-05-11 Thread Salz, Rich
> I haven't been keeping my PR #512 up to date since the 1.1 code freeze, is > now a good time to start again? If it's a feature, wait until after 1.1 and then rebase. If it's a bug or doc fix or similar, please update now and ping. -- openssl-dev mailing list To unsubscribe: https://mta.openss

Re: [openssl-dev] How to contribute patches has changed

2016-05-11 Thread Joey Yandle
The summary could be phrase as “just open a GitHub PR, no need to deal with RT” I haven't been keeping my PR #512 up to date since the 1.1 code freeze, is now a good time to start again? cheers, Joey -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl

[openssl-dev] How to contribute patches has changed

2016-05-11 Thread Salz, Rich
We've updated our preferred way to submit patches. Please see the CONTRIBUTING file, which you can find here (among other places): https://github.com/openssl/openssl/blob/master/CONTRIBUTING The summary could be phrase as "just open a GitHub PR, no need to deal with RT" We hope this will mak