Commit 6170fab1 authored by Glen Robertson's avatar Glen Robertson Committed by Commit Bot

Fix broken link in clang-format docs.

Change-Id: Ief702a3e9c02086063576532358da0eb5f12402c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826058
Commit-Queue: Glen Robertson <glenrob@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Glen Robertson <glenrob@chromium.org>
Reviewed-by: default avatarNico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700049}
parent 7cf4d2cf
...@@ -98,7 +98,7 @@ Platform specific notes: ...@@ -98,7 +98,7 @@ Platform specific notes:
Copy the binaries into your chromium checkout (under Copy the binaries into your chromium checkout (under
`src/buildtools/(win|linux64|mac)/clang-format(.exe?)`). For each binary, you'll `src/buildtools/(win|linux64|mac)/clang-format(.exe?)`). For each binary, you'll
need to run upload_to_google_storage.py according to the instructions in need to run upload_to_google_storage.py according to the instructions in
[README.txt](https://chromium.googlesource.com/chromium/buildtools/+/master/clang_format/README.txt). [README.txt](https://chromium.googlesource.com/chromium/src/+/master/buildtools/clang_format/README.txt).
This will upload the binary into a publicly accessible google storage bucket, This will upload the binary into a publicly accessible google storage bucket,
and update `.sha1` file in your Chrome checkout. You'll check in the `.sha1` and update `.sha1` file in your Chrome checkout. You'll check in the `.sha1`
file (but NOT the clang-format binary) into source control. In order to be able file (but NOT the clang-format binary) into source control. In order to be able
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment