)]}'
{
  "log": [
    {
      "commit": "c2a4c9238d4004f0271d51a5fc9b66bb94ba3a8f",
      "tree": "d8f2ff93b297e2637efe3752d46dbd93a7fec6bb",
      "parents": [
        "415360b23157caac28899fe0e02f47f0e4532ca2"
      ],
      "author": {
        "name": "Alessio Ababilov",
        "email": "ilovegnulinux@gmail.com",
        "time": "Fri Aug 16 21:53:22 2013 +0300"
      },
      "committer": {
        "name": "Alessio Ababilov",
        "email": "ilovegnulinux@gmail.com",
        "time": "Fri Aug 16 21:57:20 2013 +0300"
      },
      "message": "Fix \u0027olso\u0027 typo in lib/oslo\n\nThis enables commit If92073be5a431840701c952a194e63a7c452c9ca\nfor cleaning up potentially installed older oslo.config. Here are\nits original details.\n\nIf the user had oslo.config installed prior to us setting up the\noslo.config out of git they can get themselves into this very funny\nsituation where pip doesn\u0027t see oslo.config 1.1.x, however some\npackages might. This manifests itself as a user error trying to\nstart nova-api which uses DeprecatedOption, not in oslo.config 1.1.x\n\nBecause of the funny state pip is in, you can\u0027t uninstall oslo.config.\n\nSo in these situations, if we see old oslo.config in the filesystem,\npip install / uninstall it to ensure that everyone ends up using the\ngit version instead.\n\nTo reduce the amount of user confusion, do this on every\ninstall_oslo for a while, which we can purge after Havana ships.\n\nChange-Id: I7fa0b70497bf5622f4638da284afe5363a004d3c\nFixes: bug #1213089\n"
    },
    {
      "commit": "025fc5e5f5d7f92f0d0bda7032cf1782b029f28a",
      "tree": "c3fcabbead67774b0cbd8dbb84f07f474040f520",
      "parents": [
        "da2b6785fcae271276b28bba69203505bb747230"
      ],
      "author": {
        "name": "Attila Fazekas",
        "email": "afazekas@redhat.com",
        "time": "Tue Aug 13 18:55:33 2013 +0200"
      },
      "committer": {
        "name": "Attila Fazekas",
        "email": "afazekas@redhat.com",
        "time": "Tue Aug 13 18:55:33 2013 +0200"
      },
      "message": "Faster old oslo.config detection\n\nJust search in the path where python searches for modules.\nLet\u0027s use python for searching, it knows the exact rules.\n\nChange-Id: I659f734c418ab5e56f4956f418af48dfbe054c8a\n"
    },
    {
      "commit": "db5fadb5cb768820df54fc3d1c7428a57b511582",
      "tree": "4df74c1f2df9bb995f983f0df3791a75dc797295",
      "parents": [
        "f3d5045ebd8693cc7e81656b4548eef055d04a9a"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sdague@linux.vnet.ibm.com",
        "time": "Fri Aug 09 13:41:33 2013 -0400"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sdague@linux.vnet.ibm.com",
        "time": "Fri Aug 09 14:05:36 2013 -0400"
      },
      "message": "cleanup potentially installed older oslo.config\n\nIf the user had oslo.config installed prior to us setting up the\noslo.config out of git they can get themselves into this very funny\nsituation where pip doesn\u0027t see oslo.config 1.1.x, however some\npackages might. This manifests itself as a user error trying to\nstart nova-api which uses DeprecatedOption, not in oslo.config 1.1.x\n\nBecause of the funny state pip is in, you can\u0027t uninstall oslo.config.\n\nSo in these situations, if we see old oslo.config in the filesystem,\npip install / uninstall it to ensure that everyone ends up using the\ngit version instead.\n\nTo reduce the amount of user confusion, do this on every\ninstall_oslo for a while, which we can purge after Havana ships.\n\nChange-Id: If92073be5a431840701c952a194e63a7c452c9ca\n"
    },
    {
      "commit": "1b6b5318a05adbc049fd35ca62ed30852ea1026a",
      "tree": "97faffb9cef20fc220ed93363b4784d6e945dcea",
      "parents": [
        "e7559a479edec699f5b002daa1cf6518b39fb366"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sdague@linux.vnet.ibm.com",
        "time": "Wed Jul 31 06:46:34 2013 -0400"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sdague@linux.vnet.ibm.com",
        "time": "Wed Jul 31 07:32:20 2013 -0400"
      },
      "message": "install oslo from upstream in devstack\n\nthe libraries that have graduated from oslo incubation need to be\nmade available in devstack so that projects can develop against\nupstream versions of these libraries, and that we can test their\ncompatibility in the gate.\n\nThis should also allow us to force global requirements on all the\nprojects during installation.\n\nChange-Id: Idf527b16b50eb58564ec74428290cd31424f5de2\n"
    }
  ]
}