)]}'
{
  "commit": "b6155e60f3eab82ce35c27de90b642f59d26598b",
  "tree": "ef6ce8dd100d230d134c0c49d0dcc32b00b435ec",
  "parents": [
    "4e98e5c903785a96a3e263a892941e90af56cb5f"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@chromium.org",
    "time": "Fri Dec 25 00:58:34 2015 -0500"
  },
  "committer": {
    "name": "Adam Langley",
    "email": "alangley@gmail.com",
    "time": "Thu Jan 28 00:29:34 2016 +0000"
  },
  "message": "Remove app_data from EVP_PKEY_CTX.\n\nIt\u0027s never used. It\u0027s not clear why one would want such a thing.\nEVP_PKEY_CTX has no way for callers to register callbacks, which means\nthere shouldn\u0027t be a way for the library to present you an EVP_PKEY_CTX\nout-of-context. (Whereas app_data/ex_data makes sense on SSL because of\nits numerous callbacks or RSA because of RSA_METHOD.)\n\nChange-Id: I55af537ab101682677af34f6ac1f2c27b5899a89\nReviewed-on: https://boringssl-review.googlesource.com/6849\nReviewed-by: Adam Langley \u003calangley@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e2f4bee6ca0093dadd7c1a3beb443879ca4254f4",
      "old_mode": 33188,
      "old_path": "crypto/evp/evp_ctx.c",
      "new_id": "b06eefd6a2caddee25d9ff490f60e8fed3bc7427",
      "new_mode": 33188,
      "new_path": "crypto/evp/evp_ctx.c"
    },
    {
      "type": "modify",
      "old_id": "fa57ae9645dab3f5733f3b34f4b64cf749b9dd9b",
      "old_mode": 33188,
      "old_path": "crypto/evp/internal.h",
      "new_id": "3acc36140a988309454b93678e90a73c441de8de",
      "new_mode": 33188,
      "new_path": "crypto/evp/internal.h"
    },
    {
      "type": "modify",
      "old_id": "adf586e83407c0b3d258f930e8504d27869dd98e",
      "old_mode": 33188,
      "old_path": "include/openssl/evp.h",
      "new_id": "2ec886167d2864d1ef61fed1bb205223572f3966",
      "new_mode": 33188,
      "new_path": "include/openssl/evp.h"
    }
  ]
}