[roll] Roll fuchsia [zither] Namespace backends under "backends"

This change is a pure move for aesthetic/organizational purposes. The
top-level zither directory was getting a bit cluttered, and the
namespacing of backends under a "backends" subdirectory helps to
reinforce that these relate to separate codebases (rather than
constituent ones).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/780682
Original-Revision: 705643700adb1724dbc0ed1c9619d41af5220104
GitOrigin-RevId: 9164526b004563727b4c3032436992eaad2f70c8
Change-Id: I426e0f9cb283d443601ebb449ed9d02f49376607
1 file changed
tree: 3f3bde11b4a48e594e1785964bd0029c12dd9dd8
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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 via the IRC channel #fuchsia on Freenode.

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.