From 6ef767f9fa50583959d2cb27581e88436fea08a1 Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Wed, 11 May 2016 15:32:32 -1000 Subject: [PATCH] Clarify misleading note in README.md about BoringSSL compat. It was true at the beginning, but now is very untrue. --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 0b91703f89..ccaf5d883c 100644 --- a/README.md +++ b/README.md @@ -21,11 +21,9 @@ Particular attention is being paid to making it easy to build and integrate The name *ring* comes from the fact that *ring* started as a subset of BoringSSL, and *"ring"* is a substring of "Bo*ring*SSL". Almost all the code in -*ring* comes from BoringSSL, and BoringSSL is derived from OpenSSL. In general -an application that uses the subset of BoringSSL APIs that *ring* supports -should work identically if it is recompiled and relinked with BoringSSL -instead. *ring* tracks upstream changes to BoringSSL. Several patches that -were developed for *ring* have already been integrated upstream in BoringSSL. +*ring* comes from BoringSSL, and BoringSSL is derived from OpenSSL. *ring* +tracks upstream changes to BoringSSL. Several patches that were developed for +*ring* have already been integrated upstream in BoringSSL (over 170 so far).