From: Rich Salz Date: Tue, 9 Sep 2014 21:41:46 +0000 (-0400) Subject: RT2196: Clear up some README wording X-Git-Tag: OpenSSL_1_0_2-beta3~35 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=3aa2d2d08f56602f128e4a3ea5e22f4299ea8a7f;p=oweals%2Fopenssl.git RT2196: Clear up some README wording Say where to email bug reports. Mention general RT tracker info in a separate paragraph. Reviewed-by: Tim Hudson (cherry picked from commit 468ab1c20d1f3a43a63d0516fed6c9fefb3ccf71) --- diff --git a/README b/README index e4aaf921a4..ef0ad3ce30 100644 --- a/README +++ b/README @@ -135,8 +135,7 @@ - Problem Description (steps that will reproduce the problem, if known) - Stack Traceback (if the application dumps core) - Report the bug to the OpenSSL project via the Request Tracker - (http://www.openssl.org/support/rt.html) by mail to: + Email the report to: openssl-bugs@openssl.org @@ -144,10 +143,11 @@ or support queries. Just because something doesn't work the way you expect does not mean it is necessarily a bug in OpenSSL. - Note that mail to openssl-bugs@openssl.org is recorded in the publicly - readable request tracker database and is forwarded to a public - mailing list. Confidential mail may be sent to openssl-security@openssl.org - (PGP key available from the key servers). + Note that mail to openssl-bugs@openssl.org is recorded in the public + request tracker database (see https://www.openssl.org/support/rt.html + for details) and also forwarded to a public mailing list. Confidential + mail may be sent to openssl-security@openssl.org (PGP key available from + the key servers). HOW TO CONTRIBUTE TO OpenSSL ----------------------------