|author||Curtis Malainey <firstname.lastname@example.org>||Thu Jun 06 23:42:42 2019|
|committer||Commit Bot <email@example.com>||Mon Jun 10 14:51:58 2019|
manifest: remove sound-open-firmware-tools This repo has been archived upstream (merged into the firmware repo) and we never got to integrate local SOF building before that happened. Therefore the repo is dead and no longer needed. BUG=chromium:967158 TEST=None Change-Id: I8bf5b233f4a4133bd5c43a36459fe6c38a64a01b Signed-off-by: Curtis Malainey <firstname.lastname@example.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/1648946 Reviewed-by: Kirtika Ruchandani <email@example.com> Reviewed-by: Ned Nguyen <firstname.lastname@example.org> Tested-by: Kirtika Ruchandani <email@example.com> Commit-Queue: Kirtika Ruchandani <firstname.lastname@example.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.