)]}'
{
  "commit": "d3a5b87aed103460a12dc2ca29ce4ae94733b304",
  "tree": "6b3eafcbdc1ccfec7b38cf817fcebb7843241915",
  "parents": [
    "a0b49d63fdc33e54eac93674c86891d15d181d87"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "alangley@gmail.com",
    "time": "Tue Aug 11 16:20:14 2020 -0700"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Wed Aug 12 15:14:38 2020 +0000"
  },
  "message": "Handle NULL arguments in some i2d_* functions.\n\nPrior to 5d7c2f8b1d, these i2d functions would fail, rather than crash,\nif passed a NULL argument. While we don\u0027t generally have much truck with\nthe idea that functions should be expected to handle NULL arguments\nwhere not documented, it seems that a fair amount of code is depending\non this.\n\nChange-Id: I928b35533aa2a7beed57d7f58ba44681a8eb05c6\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42464\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4d13d59fd4bcb171e831e494ea820374004fed93",
      "old_mode": 33188,
      "old_path": "crypto/evp/evp_asn1.c",
      "new_id": "2f3e115ec7365a6530a0d6ffdded05ec44f47a6c",
      "new_mode": 33188,
      "new_path": "crypto/evp/evp_asn1.c"
    }
  ]
}