|author||Bhanu Prakash Maiya <firstname.lastname@example.org>||Mon Jun 06 17:01:59 2022|
|committer||Chromeos LUCI <email@example.com>||Mon Jun 06 17:23:50 2022|
full: Remove unused system/bt repository Bluetooth moved to aosp/packages/modules/Bluetooth and it looks like removing the old repo was missed. Doing cleanup here of an unused repo. BUG=b:206135094 TEST=CQ Change-Id: Ie81676a4ef8c4d44634f94bb4e66e1f5576b6bbc Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/3691755 Reviewed-by: Jonathon Murphy <firstname.lastname@example.org> Tested-by: Bhanu Prakash Maiya <email@example.com> Auto-Submit: Bhanu Prakash Maiya <firstname.lastname@example.org> Commit-Queue: Jonathon Murphy <email@example.com>
Repo is the tool that we use to manage our local checkouts. It parses the manifest specified by the
default.xml file. The name of the manifest can be overridden using
-m. One could also check out a subset of the manifest using the repo
groups feature. This section documents the important groups that are part of the default chromiumos manifest.
This group is the minimum subset of repos needed to do a full build of Chrome OS. It doesn't include all of the repos to necessarily test the OS image but does include all those needed to create an image.
The subset of repos needed to perform release actions i.e. payload generation, etc. Used by release engineers, TPMs, and Infra team members. Note this group isn't useful without a checkout of manifest-internal.
Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.