commit | 2f569d80f9600853d764f92785f07823a4801910 | [log] [tgz] |
---|---|---|
author | Tiago Vignatti <tvignatti@igalia.com> | Tue Jan 23 13:23:21 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 23 13:23:21 2024 |
tree | 2384c07f4bbcf32c82d87a3050bf1564fe76a3e7 | |
parent | 8d774fd740fc13200670a01ce363304a24ad51f8 [diff] |
Rename //net/base/mac directory to //net/base/apple (3/n) This renames the remaining directory in //net/base used both by macOS and iOS, following the naming convention and changing it something more suggestive. Like suggested by mark@, this renaming process will be carried on in three steps: 1. Rename net/base/mac to net/base/apple, creating new temporary forwarding headers in net/base/mac that #include net/base/apple. 2. Convert all of the use sites from net/base/mac to net/base/apple. This can be done across multiple ch anges if desirable, which could make things more manageable for reviewers. The changes here are performing this step in //components, //content and //ios/components directories, using the following command: LC_CTYPE=C find . -type f -exec sed -i "" "s:net/base/mac/:net/base/apple/:g" {} \; 3. Remove the temporary forwarding headers in net/base/mac, so that we’re only left with net/base/apple. Bug: 1519486 Change-Id: Ic9b8e9fac3277ebfef31507d4ebe226787aeb43b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5216956 Commit-Queue: Tiago Vignatti <tvignatti@igalia.com> Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Ali Juma <ajuma@chromium.org> Cr-Commit-Position: refs/heads/main@{#1250775}
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.