)]}'
{
  "commit": "c9a7dd687987666df5910f2b35fdc8c3d1e5ed05",
  "tree": "615e67f649bcf127981b3d3a41f709b50c9a9d70",
  "parents": [
    "4984e4a6325e9c6302f846c7bf2b75e8ea3fd9dd"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Sat Mar 19 18:46:57 2022 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Mar 25 16:19:16 2022 +0000"
  },
  "message": "Retire the Windows BIO_printf workaround.\n\nWith the UCRT, introduced in VS 2015, vsnprintf in MSVC is now\nC99-conformant. See:\nhttps://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/vsnprintf-vsnprintf-vsnprintf-l-vsnwprintf-vsnwprintf-l?view\u003dmsvc-170\n\nIt is a little unclear to me whether \"Beginning with the UCRT in Visual\nStudio 2015 and Windows 10\" means it is only C99-conformant in Windows\n10, or if this is referring to how the UCRT starts becoming an OS\ncomponent in Windows 10. I think the latter. This document talks about\nthe UCRT:\nhttps://docs.microsoft.com/en-us/cpp/porting/upgrade-your-code-to-the-universal-crt?view\u003dmsvc-170\n\nBut we have tests which cover this in BIOTest.Printf. If it\u0027s not\nC99-compliant in Windows 7, we\u0027ll notice in Chromium\u0027s CI.\n\nChange-Id: I932ec2633f94bd77dbe797b06a6bfbc95a568335\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52086\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4f9d8a18715b0592602aa9977219a48e261800b1",
      "old_mode": 33188,
      "old_path": "crypto/bio/printf.c",
      "new_id": "253546b7cf141d860fd5f4e0a81d145ac54b43f5",
      "new_mode": 33188,
      "new_path": "crypto/bio/printf.c"
    }
  ]
}