|author||Edman Anjos <firstname.lastname@example.org>||Fri Jul 19 20:14:54 2019|
|committer||Commit Bot <email@example.com>||Tue Jul 23 13:54:06 2019|
Change src/aosp/system/keymaster to pie-release branch Keymaster is currently mirroring aosp/master, but should point to a P branch instead. BUG=b:110136496 TEST=repo sync src/aosp/system/keymaster Change-Id: I490294fe21a8a1cc7fcd4eb4ae64b11dd114f203 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/1709373 Reviewed-by: Mike Frysinger <firstname.lastname@example.org> Commit-Queue: Edman Anjos <email@example.com> Tested-by: Edman Anjos <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.