commit | 569864454beb7937fd58e487afb22d961aa07bcb | [log] [tgz] |
---|---|---|
author | Yu-Ping Wu <yupingso@chromium.org> | Tue May 10 15:44:29 2022 +0800 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 11 02:46:30 2022 +0000 |
tree | 3ac964aea3b84229fe94fa95614393a1137cab64 | |
parent | b03befeff1d576cdd3264327b04718e936c22bfe [diff] |
firmware: Correct firmware updater name The local firmware updater "updater.sh" may not always exist (CL:3592736), so correct the updater name to the formal one, "chromeos-firmwareupdate". BUG=b:229686920 TEST=none Change-Id: Ic27bf466b2ec0bdd17c5c77d5237b90f87b27372 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3637029 Reviewed-by: Jack Neus <jackneus@google.com> Auto-Submit: Yu-Ping Wu <yupingso@chromium.org> Commit-Queue: Yu-Ping Wu <yupingso@chromium.org>
This repository exists in two locations in the tree: infra/proto
, and chromite/infra/proto
. The infra/proto
repository is always at ToT, while the chromite/infra/proto
checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.
When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto
checkout. Chromite generates its proto bindings from the chromite/infra/proto
repo.