)]}'
{
  "commit": "9132654c7968e8b510ce015a2fa6708a96c20971",
  "tree": "8d6079f0456d680c6b111bf11e40fe1e93e7f25b",
  "parents": [
    "db06153cd17bd3e2d8796ff6a6be1738813d2751"
  ],
  "author": {
    "name": "QUICHE team",
    "email": "quiche-dev@google.com",
    "time": "Mon Mar 25 11:37:44 2019 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Mar 25 11:38:16 2019 -0700"
  },
  "message": "Use \u0027bytes\u0027 instead of \u0027string\u0027 for holding binary data\n\nProto \u0027string\u0027 fields are required to contain valid UTF-8 data, while \u0027bytes\u0027 fields are allowed to contain arbitrary data.  Since both proto types are expressed in C++ the same way, this should have no effect other than stopping this warning message:\n\nE0325 09:52:56.156763    4987 wire_format_lite.cc:625] String field \u0027quic.QuicServerConfigProtobuf.PrivateKey.private_key\u0027 contains invalid UTF-8 data when serializing a protocol buffer. Use the \u0027bytes\u0027 type if you intend to send raw bytes.\n\ngfe-relnote: No-op proto change, not flag-protected.\nPiperOrigin-RevId: 240184602\nChange-Id: Ib77b16245c21eef473160a39e9b777611d3899c5\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "06db4a731993de239d870d44a6f24d7d14e7a5c5",
      "old_mode": 33188,
      "old_path": "quic/core/proto/crypto_server_config.proto",
      "new_id": "bb447dcc4b6818cf5fb0bc7d693b3cff4d18e3d5",
      "new_mode": 33188,
      "new_path": "quic/core/proto/crypto_server_config.proto"
    }
  ]
}