)]}'
{
  "commit": "ff06ea219763559bec2aab26dde1cec8608405e9",
  "tree": "47721d5fd7ddf3a4018eac3f495f2cef93400379",
  "parents": [
    "6908d9ce4c26a8bc00e3616bc0764bbb292d6bfd"
  ],
  "author": {
    "name": "Anthony Liguori",
    "email": "aliguori@us.ibm.com",
    "time": "Mon Jan 25 08:56:53 2010 -0600"
  },
  "committer": {
    "name": "Anthony Liguori",
    "email": "aliguori@us.ibm.com",
    "time": "Tue Jan 26 14:54:59 2010 -0600"
  },
  "message": "json: escape u0000 .. u001F when outputting json\n\nMarkus Armbruster pointed out:\n\nJSON requires control characters in strings to be escaped.  RFC 4627\nsection 2.5:\n\n   A string begins and ends with quotation marks.  All Unicode\n   characters may be placed within the quotation marks except for the\n   characters that must be escaped: quotation mark, reverse solidus, and\n   the control characters (U+0000 through U+001F).\n\nWe\u0027ve been quoting the special escape sequences that JSON defines but we\nhaven\u0027t been encoding the full control character range.  This patch fixes that.\n\nSigned-off-by: Anthony Liguori \u003caliguori@us.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "60c904d3ffb6a928dc66e87a18cb9126391225e5",
      "old_mode": 33188,
      "old_path": "qjson.c",
      "new_id": "9ad8a91208e24f4ed3c57b04ccd4396445185625",
      "new_mode": 33188,
      "new_path": "qjson.c"
    }
  ]
}