commit | 0b18d79b4e87a5d9b342aadfe4454d090536439b | [log] [tgz] |
---|---|---|
author | Kirtika Ruchandani <kirtika@google.com> | Wed May 29 01:21:22 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Jun 07 00:58:59 2019 |
tree | 29b4036880733ffb1a491e7c114eeb1d8b4b78b9 | |
parent | d6f19b98d482812a880e96d4a8a920ed3cd20320 [diff] |
manifest: Remove realtek-updater This is an empty and unused repository. Using cs/ for code-search on package:chromeos_public and package:chromeos_internal shows only the following hits: - manifest - .gitmodules - .gitattributes BUG=chromium:967158 TEST=None Change-Id: I9246afdc30f74cfc6fe63a0ebfa8a084e819a0ce Signed-off-by: Kirtika Ruchandani <kirtika@google.com> Reviewed-on: https://chromium-review.googlesource.com/1633471 Commit-Ready: Kirtika Ruchandani <kirtika@chromium.org> Tested-by: Kirtika Ruchandani <kirtika@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Chris McDonald <cjmcdonald@chromium.org> Reviewed-by: Michael Mortensen <mmortensen@google.com>
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.