| commit | c4faff49d934804de044c83dcfa4598167a4c383 | [log] [tgz] |
|---|---|---|
| author | Furquan Shaikh <furquan@google.com> | Sat Mar 09 00:17:49 2019 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Mar 12 10:33:18 2019 |
| tree | 6226fe347a07a64d8fa374fed9bc33280aed92c5 | |
| parent | a4728300c0aad2dd89f301752af1e799612f5e38 [diff] |
manifest: Add CML EDK2 repo to manifest BUG=b:120584520 TEST=Verified by copying this change to .repo/manifests and doing "repo sync -m <test.xml>" that chromeos-cml-branch1 gets pulled in the right location. Change-Id: I657f188daa3b90f4b0951444e594abf5a4e53d39 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1512800 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Shelley Chen <shchen@chromium.org> Reviewed-by: Mike Frysinger <vapier@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.