commit | 2ab618b228dcb73c75a0907f85ad516b8dfe86df | [log] [tgz] |
---|---|---|
author | Alison Gale <agale@chromium.org> | Sat Apr 20 03:05:40 2024 |
committer | Copybara-Service <copybara-worker@google.com> | Sat Apr 20 03:11:17 2024 |
tree | df9000f00e42a29627172d4adf19e05a68edcce8 | |
parent | 8be54eedc0bdac41b2154310eb1883cb4e3eb6a5 [diff] |
Migrate TODOs referencing old crbug IDs to the new issue tracker IDs The canonical bug format is TODO(crbug.com/<id>). TODOs of the following forms will all be migrated to the new format: - TODO(crbug.com/<old id>) - TODO(https://crbug.com/<old id>) - TODO(crbug/<old id>) - TODO(crbug/monorail/<old id>) - TODO(<old id>) - TODO(issues.chromium.org/<old id>) - TODO(https://issues.chromium.org/<old id>) - TODO(https://issues.chromium.org/u/1/issues/<old id>) - TODO(bugs.chromium.org/<old id>) Bug id mapping is sourced from go/chrome-on-buganizer-prod-issues. See go/crbug-todo-migration for details. #crbug-todo-migration Bug: b/321899722 Change-Id: Ifd155bbeff882ea939f74cf8b8f847f42847940b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5468156 Reviewed-by: Darryl James <dljames@chromium.org> Owners-Override: Alison Gale <agale@chromium.org> Commit-Queue: Alison Gale <agale@chromium.org> Cr-Commit-Position: refs/heads/main@{#1290297} NOKEYCHECK=True GitOrigin-RevId: 59c007a7ad2f034baeffab754f3f5bf109b69cda
//build
contains:
Since this directory is DEPS'ed in by some other repositories (webrtc, pdfium, v8, etc), it should be kept as self-contained as possible by not referring to files outside of it. Some exceptions exist (//testing
, select //third_party
subdirectories), but new dependencies tend to break these other projects, and so should be avoided.
Changes to //build
should be landed in the Chromium repo. They will then be replicated to the stand-alone build repo by the gsubtreed tool. Note: You can find all directories already available through gsubtreed in the list of all chromium repos.
//build/config
- Common templates via .gni
files.//build/toolchain
- GN toolchain definitions.Other .py files
- Some are used by GN/Ninja. Some by gclient hooks, some are just random utilities.Files referenced by //.gn
:
//build/BUILDCONFIG.gn
- Included by all BUILD.gn
files.//build/secondary
- An overlay for BUILD.gn
files. Enables adding BUILD.gn
to directories that live in sub-repositories.//build_overrides
- Refer to //build_overrides/README.md.