Commit 54a566c8 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Tint from d2fa57d26dff to 62bbc6f6c050 (1 revision)

https://dawn.googlesource.com/tint.git/+log/d2fa57d26dff..62bbc6f6c050

2020-10-29 dsinclair@chromium.org Fix doc tables

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 rharrison@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: rharrison@google.com
Change-Id: I3fe30e1d973fe478483c2f08260214af05fe9930
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507102Reviewed-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@{#822177}
parent 0f6851e7
...@@ -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': 'd2fa57d26dff88826fd6274ed4b77734186f89e3', 'tint_revision': '62bbc6f6c0507b07c8d1057d8da4dc65afed4114',
# 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