BASELINE: Update Chromium to 102.0.5005.177

Change-Id: I0229f2402b8321f58c0092ec81d63372bec7e789
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

1 files changed, 0 insertions, 24 deletions

diff --git a/chromium/docs/website/site/developers/experimental-branches/index.md b/chromium/docs/website/site/developers/experimental-branches/index.md
deleted file mode 100644
index 0e962c108af..00000000000
--- a/chromium/docs/website/site/developers/experimental-branches/index.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-breadcrumbs:
-- - /developers
-  - For Developers
-page_name: experimental-branches
-title: Experimental Branches
----
-
-Sometimes it is useful to share work directly, rather than just via code
-reviews. Everyone who is a Chromium Committer has permission to push their work
-to a set of experimental refs in the chromium/src.git repository. Simply
-
-1.  Check out the branch you wish to push
-2.  git push origin HEAD:refs/experimental/**<your
-            username>**/**<branch name>**
-
-where **<your username>** is "foo@chromium.org" and **<branch
-name>** is whatever you want the ref to be called (e.g. "foo-refactor-wip").
-You'll then be able to view your push online at
-https://chromium.googlesource.com/chromium/src/+/refs/experimental/<your
-username>/<branch name>.
-
-Note that anyone, including anonymous users, can checkout or view online what
-you push to your experimental ref.
\ No newline at end of file