Commit 69afa309 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Tint from 88d705dc85ff to 1b1d2a590744 (1 revision)

https://dawn.googlesource.com/tint.git/+log/88d705dc85ff..1b1d2a590744

2020-10-23 dneto@google.com Fix doxygen comment

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/tint-chromium-autoroll
Please CC dsinclair@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Bug: None
Tbr: dsinclair@google.com
Change-Id: I0d89a433c66ef7f00403533b18898ea1bc8353ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495390Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#820364}
parent 8b20c595
...@@ -368,7 +368,7 @@ vars = { ...@@ -368,7 +368,7 @@ vars = {
'ukey2_revision': '0275885d8e6038c39b8a8ca55e75d1d4d1727f47', 'ukey2_revision': '0275885d8e6038c39b8a8ca55e75d1d4d1727f47',
# the commit queue can handle CLs rolling feed # the commit queue can handle CLs rolling feed
# and whatever else without interference from each other. # and whatever else without interference from each other.
'tint_revision': '88d705dc85ff8baa8970fe4b9d2ae6bff5d38a63', 'tint_revision': '1b1d2a59074463a1635f37eb07b65fa846682e21',
# TODO(crbug.com/941824): The values below need to be kept in sync # TODO(crbug.com/941824): The values below need to be kept in sync
# between //DEPS and //buildtools/DEPS, so if you're updating one, # between //DEPS and //buildtools/DEPS, so if you're updating one,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment