commit | e1a7bec29669d9132efb27ab13a41916cb8d3657 | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Thu Aug 23 21:56:11 2018 |
committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | Fri Sep 07 16:18:36 2018 |
tree | 82524452d021aab938cf675ff615196304bee5c3 | |
parent | da9d908be01caf3a0569d0bb45064924deeea324 [diff] |
touch_noise_filter: drop The only package that used this repo has been removed in CL:1183638. BUG=chromium:881185 TEST=tatl/tael tryjobs on R70 succeed Reviewed-on: https://chromium-review.googlesource.com/1187394 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> (cherry picked from commit 4a9048b14927651ab544ab3043d2f226f6a2d817) Conflicts: full.xml - trivial conflict due to formatting change Also update commit message for R70. Change-Id: I8cba4a52d7f02e33c006e15fa5a2c90d64b1ff4f Reviewed-on: https://chromium-review.googlesource.com/1211697 Reviewed-by: Mike Frysinger <vapier@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@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.