Update INCORPORATING.md to clarify one point.
In practice it seems that it's not clear that consumers of BoringSSL
generally check in the generated files.
Change-Id: Iaa03aa62139bbcf3e7e7f68662073854954b835f
Reviewed-on: https://boringssl-review.googlesource.com/7956
Reviewed-by: David Benjamin <davidben@google.com>
diff --git a/INCORPORATING.md b/INCORPORATING.md
index 58f37db..d53f2b5 100644
--- a/INCORPORATING.md
+++ b/INCORPORATING.md
@@ -46,6 +46,11 @@
[test](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/BUILD.generated_tests.gni)
lists generated for GN in Chromium.
+Generally one checks in these generated files alongside the hand-written build
+files. Periodically an engineer updates the BoringSSL revision, regenerates
+these files and checks in the updated result. As an example, see how this is
+done [in Chromium](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/).
+
## Defines
BoringSSL does not present a lot of configurability in order to reduce the
