)]}'
{
  "commit": "9e5eb63d011cbc6730b4fbc05c4dd3ae6021e97f",
  "tree": "b476e621c0b871b4c4943cf8ff2ce7f291939b4b",
  "parents": [
    "d879e299366895d7d80d83cfbbe05bc6a09e2a27"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Sat Mar 26 00:58:38 2016 -0400"
  },
  "committer": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Mar 31 19:35:53 2016 +0000"
  },
  "message": "Document that CRYPTO_library_init may be called concurrently.\n\nThis was fixed in 93a5b442964d9770b5faa0fb381a8c4f43e65abe, but it wasn\u0027t\ndocumented. Now that there are no pre-init functions to call like\nCRYPTO_set_neon_capable, one instance of BoringSSL may be safely shared between\nmultiple consumers. As part of that, multiple consumers need to be able to call\nCRYPTO_library_init possibly redundantlyand possibly on different threads\nwithout synchronization.\n\n(Though there is still that static initializer nuisance. It would be nice to\nreplace this with internal CRYPTO_once_t\u0027s and then CRYPTO_library_init need\nonly be called to prime armcap for a sandbox. But one thing at a time.)\n\nChange-Id: I48430182d3649c8cf19082e34da24dee48e6119e\nReviewed-on: https://boringssl-review.googlesource.com/7571\nReviewed-by: Emily Stark (Dunn) \u003cestark@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "51e10286460d4c90b84481bd23778b49c6ae760d",
      "old_mode": 33188,
      "old_path": "include/openssl/crypto.h",
      "new_id": "b52bcf80f44c596636148a7a0dc438e14d9714f8",
      "new_mode": 33188,
      "new_path": "include/openssl/crypto.h"
    }
  ]
}