|author||Tomasz Figa <firstname.lastname@example.org>||Mon May 27 05:16:14 2019|
|committer||Commit Bot <email@example.com>||Tue Jun 11 04:50:48 2019|
full.xml: Add libcamera to the manifest BUG=b:133464104 TEST=repo sync with local manifest Change-Id: I9f859fd3b4a67c3b1978fd661dda7154a1b871cf Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/1631078 Commit-Queue: Tomasz Figa <firstname.lastname@example.org> Tested-by: Tomasz Figa <email@example.com> Reviewed-by: Chris McDonald <firstname.lastname@example.org> Reviewed-by: Michael Mortensen <email@example.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.