| commit | 6584da3a66cc5076c27fc87aeb5ce9d35fa8d64d | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Tue Jun 26 06:26:38 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Jun 29 08:09:08 2018 |
| tree | 693060fb7e4b09956311ec6c8380853e2160d607 | |
| parent | a21e275f7aeeca72442b7d503a4f868c4b0db14c [diff] |
xf86-input-cmt: punt Nothing depends on this anymore, so drop it. BUG=chromium:655820 TEST=precq passes Change-Id: I3ee3f59c637ee5151a8659c3c772d1f02fcd83a3 Reviewed-on: https://chromium-review.googlesource.com/1114491 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
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 ovverriden 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 iamge.
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.