)]}'
{
  "commit": "9a85565ed3ea8cff359bcd39d4679939694df598",
  "tree": "75bc6fadd7dab22a136fe23c273b145d5bb1b63c",
  "parents": [
    "705a80f6955bf1fa63572dbc4e0729e698c1d9db"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue Nov 26 11:13:07 2024 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Nov 26 20:03:44 2024 +0000"
  },
  "message": "Don\u0027t access the read_buffer directly in read_v2_client_hello\n\nI missed a spot in https://boringssl-review.googlesource.com/21865. The\nfunction is passed an input span and should just work with that span.\nThis does the exact same thing rigth now in \u003d\u003d read_buffer.span() right\nnow. But we\u0027ll want this if we ever add a bytes-in/bytes-out API.\n\nChange-Id: Ie12ad783b77b78335beba3a27da4d205ec828077\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73547\nCommit-Queue: Bob Beck \u003cbbe@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Bob Beck \u003cbbe@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6912dc49ebfa5fecfd888167d02647dc3974af80",
      "old_mode": 33188,
      "old_path": "ssl/s3_both.cc",
      "new_id": "26b28c6189a2d3b7627d531661b58b658463f359",
      "new_mode": 33188,
      "new_path": "ssl/s3_both.cc"
    }
  ]
}