commit | a13109cfaa8b641acd65c8a43711bdc1dae24a94 | [log] [tgz] |
---|---|---|
author | John Palmer <jopalmer@chromium.org> | Mon May 24 01:16:57 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 24 01:16:57 2021 |
tree | 3f12a35152ab9ee9ad347ae1ae0aa1ae65c238f8 | |
parent | c75306b608e2909731718a5fe4ea80114c62559c [diff] |
[COIL] Change chromium code search type links to use main rather than master for components See this doc: go/chromium-coil-change for more info BUG=1210385 Change-Id: I9a04252f74e3a698744310d2d86516d174ea38b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902866 Reviewed-by: Colin Blundell <blundell@chromium.org> Commit-Queue: John Palmer <jopalmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#885850}
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.