Commit 349ec49c authored by pdfium-chromium-autoroll's avatar pdfium-chromium-autoroll Committed by Commit Bot

Roll src/third_party/pdfium 70ddc1ca22ad..84d3394d88c4 (1 commits)

https://pdfium.googlesource.com/pdfium.git/+log/70ddc1ca22ad..84d3394d88c4


git log 70ddc1ca22ad..84d3394d88c4 --date=short --no-merges --format='%ad %ae %s'
2018-07-25 art-snake@yandex-team.ru Fix hint tables parsing.


Created with:
  gclient setdep -r src/third_party/pdfium@84d3394d88c4

The AutoRoll server is located here: https://pdfium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I708980aaec069480a78688ef7c527dc2f2b6a206
Reviewed-on: https://chromium-review.googlesource.com/1149542Reviewed-by: default avatarpdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#577813}
parent 9182ff29
...@@ -129,7 +129,7 @@ vars = { ...@@ -129,7 +129,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling PDFium # the commit queue can handle CLs rolling PDFium
# and whatever else without interference from each other. # and whatever else without interference from each other.
'pdfium_revision': '70ddc1ca22ad44a77006491b604a75f6514a4aa8', 'pdfium_revision': '84d3394d88c42b798eedc938e6295ad1bf28ac66',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling openmax_dl # the commit queue can handle CLs rolling openmax_dl
# and whatever else without interference from each other. # and whatever else without interference from each other.
......
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