| commit | 49cc021b79977c89da4c37e4ae989df07b7af069 | [log] [tgz] |
|---|---|---|
| author | Stephen Barber <smbarber@chromium.org> | Fri Sep 07 18:43:34 2018 |
| committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | Fri Sep 07 19:21:30 2018 |
| tree | 9d443f13e729560bb8fe329985087c9c00b19bf4 | |
| parent | e1a7bec29669d9132efb27ab13a41916cb8d3657 [diff] |
manifest: drop logstock from R70 logstock was added to the internal manifest after branch, so it wasn't branched for R70. Remove it from the external manifest to stop sync errors. BUG=chromium:881185 TEST=tatl/tael-full tryjobs Change-Id: I7ae576ef0bb25987bc776ae70bda153a467b42fd Reviewed-on: https://chromium-review.googlesource.com/1213804 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.