commit | 2e35572c470ecfe9fc9c7bf70c05cdf5e529d3a8 | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Thu Apr 13 18:31:11 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Apr 14 20:49:32 2017 |
tree | 566b53ad4dd720271375355aa1cd222c30de8934 | |
parent | 607f325624230721c1d14586a963a0b02f634676 [diff] |
drop platform/system/core 'platform/system/core' was introduced by CL:266914 for the development of Fluoride, which has never been used on Chrome OS or is no longer in active development. BUG=chromium:673072 TEST=precq passes Change-Id: If90e6971ebd6a05438d05be63ce692cd6b65f86e Reviewed-on: https://chromium-review.googlesource.com/477290 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Ben Chan <benchan@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.