)]}'
{
  "commit": "19c3f94384d522b6d8bb7101bdb799131df2a420",
  "tree": "7359fbd7d8c47da9e0821b112575681580ceca04",
  "parents": [
    "8c1b6c62d89e4954336ae936c33a6949a605967d"
  ],
  "author": {
    "name": "Googler",
    "email": "noreply@google.com",
    "time": "Wed Mar 04 20:05:25 2015 +0000"
  },
  "committer": {
    "name": "Han-Wen Nienhuys",
    "email": "hanwen@google.com",
    "time": "Thu Mar 05 18:31:20 2015 +0000"
  },
  "message": "Change the default value for test_output to \"errors\".\n\nThis might be controversial, but I have many times seen users run their tests, and then select the failure log path in their terminal and then cat the log to their screen so they can search for their errors.  Every time, I\u0027ve pointed out, \"you can add test_output\u003derrors to your .blazerc,\" they\u0027ve thought it was great.  Sometimes they say, \"Why isn\u0027t that just the default?\"\n\n--\nMOS_MIGRATED_REVID\u003d87734723\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a12ece9f517e58cae401414142d78086c76ce18d",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java",
      "new_id": "f6ddbe9a2134d757d53228d9bd6f4ea2d15dc533",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java"
    }
  ]
}