Google Git
Sign in
chromium / chromiumos / manifest / refs/heads/factory-guybrush-14600.B
commita94c95e8f5a28022c64a68fb88acc7735e7eee5c[log] [tgz]
authorBhanu Prakash Maiya <bhanumaiya@google.com>Mon Jun 06 17:01:59 2022
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 06 17:23:50 2022
tree66c7aed0213295606b1961e8f9ea4fd3cd508ca5
parent8c056855825da74a8a89033b410b8d07036f0e9f [diff]
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 <jpmurphy@google.com>
Tested-by: Bhanu Prakash Maiya <bhanumaiya@google.com>
Auto-Submit: Bhanu Prakash Maiya <bhanumaiya@google.com>
Commit-Queue: Jonathon Murphy <jpmurphy@google.com>
1 file changed
tree: 66c7aed0213295606b1961e8f9ea4fd3cd508ca5
  1. utils/
  2. default.xml ⇨ full.xml
  3. .gitignore
  4. _kernel_upstream.xml
  5. _remotes.xml
  6. full.xml
  7. OWNERS
  8. PRESUBMIT.cfg
  9. README.md
README.md
IMPORTANT: Do not make changes to full.xml in this repo. This repo automatically syncs with the private manifest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. If you do not have access to the private repo, please ask a Googler to update the manifest on your behalf. The changes must be synced to the infra/config file chromeos_repos.star. Without this, the repo will never be picked up by CQ.

Repo Groups

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.

minilayout

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.

buildtools

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.

labtools

Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.