| commit | de11715e63f49274f3fab352f2367699348ba255 | [log] [tgz] |
|---|---|---|
| author | Nodir Turakulov <[email protected]> | Tue Sep 28 06:50:47 2021 |
| committer | Chromium LUCI CQ <[email protected]> | Tue Sep 28 06:50:47 2021 |
| tree | 535f5ae75be2239d0ce151d0f71536ddb829c658 | |
| parent | 3a090add40517005ed14519adcfcf3fae7ca0daa [diff] |
[dirmd] Use metadata mixins Use the new "mixins" feature in dirmd. Derive mixins from file:// links in OWNERS files. This CL is machine-generated, in two parts. Part 1: use mixins. 1. Save current metadata to JSON files, in ORIGINAL and REDUCED forms. dirmd read -form original > ~/tmp/dirmd/original.json dirmd read -form reduced > ~/tmp/dirmd/reduced.json 2. Run mixins.py. Source code: https://gist.github.com/nodirg/b59d3df338a72a8944f957c5b3a15e22 The script finds related directories, connected by file:// links in OWNERS files. For those directories that have the same base name, e.g. components/autofill chrome/android/java/src/org/chromium/chrome/browser/autofill if importing the "parent" to the "child" reduces metadata, or adds missing metadata, extract the common metadata to COMMON_METADATA and import it in both directories. Part2: deduplicate metadata. Apply same instructions as in https://chromium-review.googlesource.com/c/chromium/src/+/2795985/16 Bug: 1179786 Change-Id: I2e6378004ce433e02f1c9360b09eb72354083bf6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2897943 Reviewed-by: John Abd-El-Malek <[email protected]> Reviewed-by: Fred Mello <[email protected]> Owners-Override: John Abd-El-Malek <[email protected]> Commit-Queue: Nodir Turakulov <[email protected]> Cr-Commit-Position: refs/heads/main@{#925648}
ChromiumChromium 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.