manifest: Change the checkout path for CML EDK2

CML EDK2 will be using more than one branch over the lifetime of the
project. Thus, the checkout path needs to create a new directory
branch1 under edk2.

CQ-DEPEND=CL:*1037211
BUG=b:120584520
TEST=Verified that EDK2 gets checked out to branch1/ under cml/edk2.

Change-Id: I1cd311c59a394894508ee24073d9c255978a3bdc
Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1518219
Commit-Ready: Furquan Shaikh <furquan@chromium.org>
Tested-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
1 file changed
tree: b9dce04b79bbee0e68fd2fc5e2dd57190ea5313d
  1. _remotes.xml
  2. full.xml
  3. README.md
README.md
IMPORTANT: Changes to this repo must also be made in the private manfest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. Automated sync between manifest-internal and manifest is not yet set up.

Repo Groups

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.

minilayout

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.

buildtools

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.

labtools

Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.