)]}'
{
  "log": [
    {
      "commit": "a12f996778712866079711a981cdd6b58aa77419",
      "tree": "381973ca8d5af6b1fa18525ab45bd8da78bf07c2",
      "parents": [
        "c06c9e1f904a81e0fef646273b07510e90995364"
      ],
      "author": {
        "name": "Daniel P. Berrange",
        "email": "berrange@redhat.com",
        "time": "Tue Jul 01 13:21:34 2014 +0100"
      },
      "committer": {
        "name": "Daniel P. Berrange",
        "email": "berrange@redhat.com",
        "time": "Tue Jul 01 17:27:29 2014 +0100"
      },
      "message": "Avoid huge libvirtd.log files on Ubuntu hosts\n\nThe libvirt log filter settings match against the filename of\nthe libvirt source emitting the log message. Normally these\nfile names are relative to the source tree root, but in the\nUbuntu binary packages these have somehow ended up as absolute\nfilenames from the OS root. This means that a log filter of\n\u00271:libvirt\u0027 which is only intended to match src/libvirt.c\nwill in fact match every single file. This caused enourmous\nlog files on Ubuntu hosts running the gate.\n\nThe fix is to use \u00271:libvirt.c\u0027 as a more specific filename\nmatch, but we can\u0027t do this unconditionally because libvirt\n\u003e\u003d 1.2.3 does not use filenames for log filter matching\nanymore. So only change the match on Ubuntu hosts for now,\nsince that\u0027s where the original problem lies.\n\nWhile doing this, also turn off the logging of object ref\nand unref operations, since those pollute the logs with lots\nof noise.\n\nChange-Id: I71b67507a4e68a7bff0c358857aaaac08ef0c420\n"
    },
    {
      "commit": "83afcfe9a939b9af91c50eb6dfd3b435ee75b881",
      "tree": "63fbb9cf51fe06223179739a9644ea63ed585bbe",
      "parents": [
        "1469a04f183553be197166d2abeb3a6f94894d38"
      ],
      "author": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Thu Jun 12 08:47:50 2014 +1000"
      },
      "committer": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Thu Jun 12 10:25:07 2014 +1000"
      },
      "message": "[Fedora] Devstack fails to install in firewalld less system\n\nThe official F20 cloud image does not contains the firewalld,\nthere is nothing to restart, and it fails the installation.\n\nThe previous workaround change, assumed all is_fedoras has\na restartable firewalld without ensuring is it installed at all.\n\nRHEL6 even does not have a firewalld.\n\nCloses-bug: #1329102\nChange-Id: I3d119ce48af81b30bf02b01c2cd386612ac6ef90\n"
    },
    {
      "commit": "e6d99a946fb00791e52671e22b6bd848e7392b8d",
      "tree": "6d88883c727ef3aaeb7df598288d7db0c630debc",
      "parents": [
        "1e6e4289bc5783db0db35db81a91a674a3b26d02"
      ],
      "author": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Tue May 27 13:58:12 2014 +1000"
      },
      "committer": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Tue May 27 13:58:12 2014 +1000"
      },
      "message": "Remove Fedora/libvirt workaround\n\nAn updated libvirt package to address [1] is in Fedora 20 now, so we\ndon\u0027t need this work-around.  Modify the comments of the other part of\nthe work-around (restart of services) and link to the most relevant\nbug\n\n[1] https://bugzilla.redhat.com/show_bug.cgi?id\u003d1098376\n\nChange-Id: I47fba7b4f273162c2af1e37902a512041449750b\n"
    },
    {
      "commit": "3ca91b2186bb710357eda49e81694d07d8fe792b",
      "tree": "8a8c477ba74c9db2f3a4357c09566ae2bba39eca",
      "parents": [
        "f2fd04924f26aef4f74fa1b192e1fa1d76e1546c"
      ],
      "author": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Fri May 16 14:00:01 2014 +1000"
      },
      "committer": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Mon May 19 18:37:56 2014 +1000"
      },
      "message": "Workaround Fedora libvirtd issues on Xen instances\n\nFedora libvirtd fails to start on Xen instances (i.e. rackspace\ninstances) due to [1].  This works around the issue until it can be\nfixed upstream.\n\n[1] https://bugzilla.redhat.com/show_bug.cgi?id\u003d1098376\n\nChange-Id: I3790b5025982730263a6a84fce596e80f09efd5a\n"
    },
    {
      "commit": "b0f8beb8f1e851321f2d03d2ae687dc2ba2e296e",
      "tree": "bed9eab1177218184631fadbd39a893ae19759fb",
      "parents": [
        "7ee8f11588741357a321adab2fee99b3affe40b3"
      ],
      "author": {
        "name": "Adam Gandelman",
        "email": "adamg@ubuntu.com",
        "time": "Thu Mar 27 00:14:24 2014 -0700"
      },
      "committer": {
        "name": "Adam Gandelman",
        "email": "adamg@ubuntu.com",
        "time": "Thu Mar 27 00:18:22 2014 -0700"
      },
      "message": "Install qemu-kvm instead of kvm package on Ubuntu\n\nSince at least 12.04, the kvm package is a transitional dummy\npackage intended to move users to the newer qemu-kvm package.  This\nremoves the dependency on this dummy package, which will be going away\nin 14.04, and instead depends on the proper qemu-kvm package.\n\nChange-Id: I4a88ada3cf32106413a9fae6fe77c9c4c28a524e\nCloses-bug: #1294557\n"
    },
    {
      "commit": "0f73ff2c516cb9fdb6849f7feb19cd0cfde46852",
      "tree": "f288eba6f831ce13fdb7a5770e5a8ffba19f3348",
      "parents": [
        "f8afb8bee1de1ccad21c71abb5ba0b1f54296a02"
      ],
      "author": {
        "name": "Adam Gandelman",
        "email": "adamg@ubuntu.com",
        "time": "Thu Mar 13 14:20:43 2014 -0700"
      },
      "committer": {
        "name": "Adam Gandelman",
        "email": "adamg@ubuntu.com",
        "time": "Thu Mar 13 15:03:55 2014 -0700"
      },
      "message": "Move libvirt install + setup to functions-libvirt\n\nMoves installation and setup of libvirt to a common functions-libvirt,\nwhich can be used by other drivers in the future that may require\ncross-distro libvirt installation and config but are not using\nVIRT_DRIVER\u003dlibvirt (ie, Ironic).\n\nChange-Id: I4a9255c8b4bacd5acfde9b8061c9e537aeea592c\n"
    }
  ]
}