[sync] Rename components/sync/driver to components/sync/service It was agreed within the Sync team that the name 'driver' conveys little and is a historic artifact. The new name, 'service', reflects what most dependent targets care about: SyncService and adjacent APIs. Semi-automated patch generated via: git mv components/sync/driver components/sync/service ./tools/git/mass-rename.py cat /tmp/affected-files.txt | \ xargs sed -i 's/#include/#import/g' git grep -l 'sync/driver' |\ xargs sed -i 's/components\/sync\/driver/components\/sync\/service/g' git grep -l 'sync_driver_sync_internals' |\ xargs sed -i 's/sync_driver_sync_internals/sync_service_sync_internals/g' git grep -l 'components/sync/service:driver' |\ xargs sed -i 's/sync\/service:driver/sync\/service/g' git grep -l 'kSyncDriverSyncInternalsResources' |\ xargs sed -i\ 's/kSyncDriverSyncInternalsResources/kSyncServiceSyncInternalsResources/g' git grep -l 'IDR_SYNC_DRIVER_SYNC' | \ xargs sed -i 's/IDR_SYNC_DRIVER_SYNC/IDR_SYNC_SERVICE_SYNC/g' sed -i 's/driver/service/g' components/sync/service/BUILD.gn\ components/sync/service/sync_api_component_factory.h sed -i 's/_H__/_H_/g' components/sync/service/*.h git cl format Manual changes include: 1. Build target rename in components/sync/driver/BUILD.gn. 2. Header guard issues surfaced by presubmit. 3. Several header files reintroduced to avoid breaking downstream. Disable-Rts: True Change-Id: If23629e79e781e55c3d783e3074fb536311928d6 Bug: 1444709 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4518214 Reviewed-by: Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by: Marc Treib <treib@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Reviewed-by: Weilun Shi <sweilun@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1144710}
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.