)]}'
{
  "commit": "68b78719e8751b40344437408ed7f2aa1e7083a4",
  "tree": "de3bc28d32e58e78b2d1db6936c29f06af9a5ace",
  "parents": [
    "8ba42859172b75f6cc85824fb0954e1e22b93646"
  ],
  "author": {
    "name": "Alan Screen",
    "email": "awscreen@chromium.org",
    "time": "Sat Jan 28 03:59:30 2023 +0000"
  },
  "committer": {
    "name": "Pdfium LUCI CQ",
    "email": "pdfium-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Sat Jan 28 03:59:30 2023 +0000"
  },
  "message": "Specify output name for pdfium build component\n\nStarting with crrev.com/1096860, the Chromium build rules can modify the\nresulting name of the built component.  In places where loading the\npdfium component library is hardcoded, the options are:\n- modify the name in the source code where it is loaded, to follow\n  the new naming scheme;\n- use output_name in PDFium build rules to explicitly specify the\n  name of the library, so that Chromium won\u0027t modify its name.\n\nUse of the output_name approach is easier to understand when seeing the\npdfium component name hard-coded in source.  It also protects such code\nblocks from any further modifications to the build rule.\n\nBug: chromium:1410951\nChange-Id: Ib9a2375c760d58a521815dc08f3b8c5d31d3f36a\nReviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/103501\nCommit-Queue: Alan Screen \u003cawscreen@chromium.org\u003e\nReviewed-by: Lei Zhang \u003cthestig@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0cd3fa9994cfb3825d04be2f9144e186cc81e05e",
      "old_mode": 33188,
      "old_path": "BUILD.gn",
      "new_id": "62210c2f65c917e395ea911bbe4057bdf9f13b36",
      "new_mode": 33188,
      "new_path": "BUILD.gn"
    }
  ]
}