commit | a21e275f7aeeca72442b7d503a4f868c4b0db14c | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Tue Jun 26 06:36:26 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Jun 28 05:07:36 2018 |
tree | 5e90d8c9ec190f7c233a95108dbe0665a05421fb | |
parent | 41bb46b3ba9f0e191675873c8183bf9122083012 [diff] |
tegrastats/tegra-power-query: punt These haven't been used since the tegra2 days (which we didn't ship). BUG=None TEST=precq passes Change-Id: I1d1b66ddf3f675a7d6844c644b8fe1d8e1ac75af Reviewed-on: https://chromium-review.googlesource.com/1114494 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Douglas Anderson <dianders@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.