[roll] Roll fuchsia [logs] Remove duplicate LogSink routes

Routing LogSink manually is not needed,
as this is done implicitly through the client shard.
Future CLs will update the routing used in the shard,
so it's necessary to cleanup these duplicate routes
in order to update the shards.

Original-Bug: b/345827642
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1129856
Owners-Override: James Robinson <jamesr@google.com>
Original-Revision: 1e027c6732f55cf5f5dec607c96f9aee8ed87c16
GitOrigin-RevId: df084511108cef7911fc4f9d372987a9ed40b855
Change-Id: I9fd6bcedff1e18fc3e5fd00eebff051edbfe3ea3
1 file changed
tree: e425f7e79f95bed51c38e6afa4891ab5f929ce85
  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.