commit e9f816b12b3e68de575d21e2a9b7d76e4e5c58ac
author Bob Beck <bbe@google.com> Tue Jul 18 17:56:09 2023 +0000
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Thu Jul 20 21:54:39 2023 +0000
tree 1858843876c430d1f46470914f362be2bbe0876c
parent 4d70016a62bf8d4c1856aff89d6769ad4f71e77f

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>

INCORPORATING.md

diff --git a/INCORPORATING.md b/INCORPORATING.md
index f793e88..96c6435 100644
--- a/INCORPORATING.md
+++ b/INCORPORATING.md
@@ -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