0e7d7771e9
This is recommended by the sync integration checklist [1], in order to ease refactorings etc that need to touch all bridges. (Recent example which triggered this: crbug.com/347649753) [1] https://www.chromium.org/developers/design-documents/sync/integration-checklist/ Bug: none Change-Id: Iba280d2207ccaa24139a79dd9caab07de8223ff8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5666518 Reviewed-by: Jon Mann <jonmann@chromium.org> Reviewed-by: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org> Auto-Submit: Marc Treib <treib@chromium.org> Reviewed-by: Victor Vianna <victorvianna@google.com> Reviewed-by: Piotr Pawliczek <pawliczek@chromium.org> Reviewed-by: Mikel Astiz <mastiz@chromium.org> Reviewed-by: Matthew Zhu <zhumatthew@google.com> Reviewed-by: Matthew Jones <mdjones@chromium.org> Reviewed-by: Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/main@{#1324344}
Chromium
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.
If you found a bug, please file it at https://crbug.com/new.