aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2017-09-25 11:57:23 -0400
committerRuss Cox <rsc@golang.org>2017-09-25 19:27:58 +0000
commitd724c60b4d303f3acee0f3cef09f7a724b892fb3 (patch)
treeaaa99f5afef9a3bd2486c2555b46e930bb4b6e26
parent70bada9db3b9eda9ae024dca36eb8fc1d57101c2 (diff)
downloadgo-d724c60b4d303f3acee0f3cef09f7a724b892fb3.tar.gz
go-d724c60b4d303f3acee0f3cef09f7a724b892fb3.zip
[dev.boringcrypto] misc/boring: update README
Change-Id: I17158d73f2541d49188daa2e4e02ca389f1c395d Reviewed-on: https://go-review.googlesource.com/65992 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-rw-r--r--misc/boring/README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/misc/boring/README.md b/misc/boring/README.md
index 612323573e..698b6617f9 100644
--- a/misc/boring/README.md
+++ b/misc/boring/README.md
@@ -51,9 +51,10 @@ To issue new BoringCrypto releases based on Go 1.8:
BoringCrypto updates, including the update of the `VERSION` file.
Mail them out and get them committed.
-3. **Back on the (not Go 1.8) dev.boringcrypto branch**, run `build.release <commit>`,
+3. **Back on the (not Go 1.8) dev.boringcrypto branch**,
+run `make.bash` and then `build.release <commit>`,
where `<commit>` is the latest commit on the dev.boringcrypto.go1.8 branch.
-It will build a release and upload it.
+The script will build a release and upload it.
4. Run `build.docker`.