Roll src/third_party/pdfium/ c49f39dff..b3a524083 (2 commits)

https://pdfium.googlesource.com/pdfium.git/+log/c49f39dff730..b3a5240832fc

$ git log c49f39dff..b3a524083 --date=short --no-merges --format='%ad %ae %s'
2018-03-19 ralf.sippl Calculate AP for multi-line markup annotations correctly
2018-03-19 thestig Roll DEPS for Clang to 7d56ff90.

Created with:
  roll-dep src/third_party/pdfium


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: I3519f4d3ca31557ab8a613027c610c20d592f60f
Reviewed-on: https://chromium-review.googlesource.com/969829Reviewed-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@{#544266}
parent 143023cc
...@@ -103,7 +103,7 @@ vars = { ...@@ -103,7 +103,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': 'c49f39dff730a71b0198521f5ec0e2142c0c0d26', 'pdfium_revision': 'b3a5240832fce3f0b706c16070a1e69c2c1edb86',
# 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