commit | 57086b30e829fd231e409a7f918fa3f1937cdf63 | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Wed Feb 27 22:09:30 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Mar 05 20:58:18 2019 |
tree | 8896ae36556e0d20a1c462ae8f3d67aac8f7478c | |
parent | 6b7c36ef19bcc00acedc53b306d5a10be0184950 [diff] |
move clang-format dir under the new buildtools path We expect the clang-format script in the same tree as buildtools. BUG=chromium:930818 TEST=precq passes CQ-DEPEND=CL:1475867 Change-Id: Ica5581db172f8fbde0928087ba536760141358a4 Reviewed-on: https://chromium-review.googlesource.com/1491950 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: LaMont Jones <lamontjones@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.