commit | 22b50788ffc0952ef1a55d7ac0940b63d5fd0336 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Mar 12 09:55:18 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 12 09:55:18 2021 |
tree | cd70e39896f919f4ff4095bca315376043f5feef | |
parent | 1795a2f85eb10f422dfaffe50c5038acd73336a3 [diff] |
Roll DevTools Frontend from b417167d58fa to 9b0ae2b193c9 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/b417167d58fa..9b0ae2b193c9 2021-03-12 wolfi@chromium.org Remove non-exisiting file from license-header check If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1159334 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I8a5686801fbd989c7d1d089f30e7b8d23358eeb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2756008 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#862361}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.