Use HTTPS links for Google domains in docs
Since almost all Google domains support HTTPS, and it is a good practice to
use HTTPS wherever possible, thus in this patch, I changed most HTTP links
to https whose domains are known to support HTTPS well.
Modifications are generated by running these commands in src/docs directory:
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/www.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/www.chromium.org/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/developer.android.com/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/developer.android.com/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/dev.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/dev.chromium.org/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/build.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/build.chromium.org/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/src.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/src.chromium.org/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/crbug.com/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/crbug.com/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/groups.google.com/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/groups.google.com/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/cs.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/cs.chromium.org/g' *.md
sed -i 's/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/http\/codereview.chromium.org/https:\/\/blue-sea-697d.quartiers047.workers.dev:443\/https\/codereview.chromium.org/g' *.md
BUG=
Review-Url: https://codereview.chromium.org/2545363002
Cr-Commit-Position: refs/heads/master@{#436501}
diff --git a/docs/clang.md b/docs/clang.md
index 0661253..685362f 100644
--- a/docs/clang.md
+++ b/docs/clang.md
@@ -36,12 +36,12 @@
## Mailing List
-http://groups.google.com/a/chromium.org/group/clang/topics
+https://groups.google.com/a/chromium.org/group/clang/topics
## Using plugins
The
-[chromium style plugin](http://dev.chromium.org/developers/coding-style/chromium-style-checker-errors)
+[chromium style plugin](https://dev.chromium.org/developers/coding-style/chromium-style-checker-errors)
is used by default when clang is used.
If you're working on the plugin, you can build it locally like so:
@@ -68,7 +68,7 @@
Things should compile, and all tests should pass. You can check these bots for
how things are currently looking:
-http://build.chromium.org/p/chromium.fyi/console?category=win%20clang
+https://build.chromium.org/p/chromium.fyi/console?category=win%20clang
```shell
python tools\clang\scripts\update.py
