mirror of
https://github.com/AntelopeIO/boringssl.git
synced 2026-07-21 14:43:53 +00:00
Link Googlers to the new porting policy doc
Change-Id: Ic461a3890aa78109dc06ffcf144b6b7a90456ff3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61748 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: Bob Beck <bbe@google.com>
This commit is contained in:
committed by
Boringssl LUCI CQ
parent
4d70016a62
commit
e9f816b12b
@@ -3,6 +3,11 @@
|
||||
**Note**: if your target project is not a Google project then first read the
|
||||
[main README](/README.md) about the purpose of BoringSSL.
|
||||
|
||||
If you are porting BoringSSL to a new platform see
|
||||
["go/boringssl-on-new-platform"](https://goto.corp.google.com/boringssl-on-new-platform) (Google
|
||||
Internal) for information about porting BoringSSL to a new platform for a Google
|
||||
project.
|
||||
|
||||
## Which branch to use
|
||||
|
||||
BoringSSL usage typically follows a
|
||||
|
||||
Reference in New Issue
Block a user