)]}'
{
  "log": [
    {
      "commit": "ec1df9b7f6310ce5dd9432b727eb9f7bde9f2796",
      "tree": "ea0c10b715d35b6a9b4f92c73b2732b0c53f4966",
      "parents": [
        "06d029c1c8c06a6d446b7cc4d5e763ff0754b149"
      ],
      "author": {
        "name": "Doug Anderson",
        "email": "dianders@google.com",
        "time": "Wed Oct 27 17:13:07 2010 -0700"
      },
      "committer": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Fri Oct 29 08:15:14 2010 -0700"
      },
      "message": "Don\u0027t allow git fetch to start ControlMaster\n\nTo avoid connectivity problems, we don\u0027t want the ssh process\nthat is started by git fetch to become a ControlMaster for the\noverall sync task.  If it did, we would lose connectivity when\ngit fetch was finished with the current project, causing later\nprojects to not fetch efficiently.\n\nChange-Id: I8d0dcf9b361276ff8c8b5a6324cbd4a501e9c4dd\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n"
    },
    {
      "commit": "fb2316146f6e3036e0cc3e08653920964a428a15",
      "tree": "f19c5c65a035f547ada03496f1576524e4602665",
      "parents": [
        "8bd5e60b16080008771afcaa7de7084487b84780"
      ],
      "author": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Fri Apr 10 18:53:46 2009 -0700"
      },
      "committer": {
        "name": "Shawn O. Pearce",
        "email": "sop@google.com",
        "time": "Sat Apr 18 16:50:47 2009 -0700"
      },
      "message": "Automatically use SSH control master support during sync\n\nBy creating a background ssh \"control master\" process which lives\nfor the duration of our sync cycle we can easily cut the time for\na no-op sync of 132 projects from 60s to 18s.\n\nBug: REPO-11\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n"
    }
  ]
}
