commit | d80a13a1951d7e238659e03fb580abfa7fabfc07 | [log] [tgz] |
---|---|---|
author | Chad Versace <chadversary@chromium.org> | Wed Nov 22 18:37:33 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Nov 30 09:13:02 2017 |
tree | c18755d61db67f0b2a543f823bd7ce1a40a9431c | |
parent | 567d7903c17e52825b745a0156da9c94a6974da5 [diff] |
arc-mesa: Move to branch arc-17.3 Update arc-mesa from branch arc-17.2.0-pre1 to branch arc-17.3, which is based on the upstream pre-release tag mesa-17.3.0-rc5. CQ-DEPEND=CL:*512717 CQ-DEPEND=CL:780840 CQ-DEPEND=CL:728102 CQ-DEPEND=CL:793895 BUG=b:69553386 TEST=repo sync; No regressions on Eve in `cts-tradefed run cts -m CtsDeqpTestCases`. Change-Id: Ia14d4b51b29957cc4681df04be7a877a530939d5 Reviewed-on: https://chromium-review.googlesource.com/786138 Commit-Ready: Nicolas Boichat <drinkcat@chromium.org> Tested-by: Chad Versace <chadversary@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@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.