From 1ad0a1d1ba53cfe2a8ae3038be80f6ea4cdfadbb Mon Sep 17 00:00:00 2001 From: krasin Date: Wed, 10 Feb 2016 14:14:17 -0800 Subject: third_party/binutils: clarify the procedure to upload the new binaries. BUG=584828 Review URL: https://codereview.chromium.org/1691533002 Cr-Commit-Position: refs/heads/master@{#374748} --- third_party/binutils/README.chromium | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'third_party/binutils') diff --git a/third_party/binutils/README.chromium b/third_party/binutils/README.chromium index 5f32f89..f5b5600 100644 --- a/third_party/binutils/README.chromium +++ b/third_party/binutils/README.chromium @@ -44,7 +44,9 @@ To upgrade binutils, use the following steps: * Remove any patches which have been merged upstream from build-all.sh * Update this README.chromium file * Run build-all.sh - * Run upload.sh + * Run upload.sh. Note: you will need write access to + gs://chromium-binutils bucket on Google Cloud Storage. To get the + access, subscribe to the internal chrome-team mailing list. * Wait for goma to have new binutils deployed (see http://go/ma). Please notify {ukai,yyanagisawa,shinyak}@chromium.org and await confirmation. -- cgit v1.1