[roll] Roll fuchsia [system-update-committer] rename configuration

This CL renames the bespoke configuration struct
which is like paver::Configuration does not support
recovery. As a reader, I found it confusing especially
because the configuration is often converted into
paver::Configuration so hopefully now both future readers
and compilers know that recovery is not supported here!!!

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1209047
Original-Revision: 9bd831fa5236691d664bab65d4d8ea3dbb002259
GitOrigin-RevId: be94001fd8134a42f4ab3860fa65f02dad328319
Change-Id: I49314a30408f0fe6782f40f0decb262f1beea18a
1 file changed
tree: 66186595f35ec922406d8a4c0d31f9a4fd9d1be7
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.