)]}'
{
  "commit": "db638238d29708a20b991af3b2488e45a8bbcf71",
  "tree": "567d8ae03a8e2480fd348ff2fe002564a5413759",
  "parents": [
    "2375765eeae11c78eec8c6bf1bdfa53cf86e6ef8"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Fri Sep 26 14:29:07 2025 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Sep 26 12:13:51 2025 -0700"
  },
  "message": "Tolerate nullptr in i2d_X509_NAME\n\nThis used to be tolerated by way of the general tasn_enc machinery. We\ndon\u0027t support this, but one existing test was relying on this to force\ni2d_X509_NAME to fail and exercise that error path. I don\u0027t think it\u0027s\nactually possible, short of malloc failure, to construct an X509_NAME\nsuch that i2d_X509_NAME fails anymore. It\u0027s easier to just restore this\nartificial failure case than to figure out what, if anything, to do with\ntheir check.\n\nChange-Id: I49bd19e711518756c5ff20230dc4df6c56bf1977\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82310\nReviewed-by: Lily Chen \u003cchlily@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Lily Chen \u003cchlily@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6b102195bdd1b8ccd1553ef7a1e09d137854386a",
      "old_mode": 33188,
      "old_path": "crypto/x509/x_name.cc",
      "new_id": "ce9b01d20c0f3294cbe5e1916331bf350c3efc64",
      "new_mode": 33188,
      "new_path": "crypto/x509/x_name.cc"
    }
  ]
}