Add wpa_supplicant-2.8 to chromeOS repo

BUG=b:132972686, chromium:877621
TEST=None

Cq-Depend: chrome-internal:1313754
Change-Id: Ic8ae74c26f9099e522fc3aed2f54cfd2c331ccfb
Reviewed-on: https://chromium-review.googlesource.com/1618100
Commit-Ready: Neeraj Poojary <npoojary@chromium.org>
Tested-by: Neeraj Poojary <npoojary@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Kirtika Ruchandani <kirtika@chromium.org>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Jason Clinton <jclinton@chromium.org>
1 file changed
tree: 530293e957a9e610217c82f87e348c006d317e78
  1. _remotes.xml
  2. full.xml
  3. OWNERS
  4. 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. And, the changes must also be synced to the infra/config file chromeos_repos.star. Without this, the repo will never be picked up by CQ.

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.