)]}'
{
  "log": [
    {
      "commit": "523f48803609b35350b624244fa73b1030c1d5fa",
      "tree": "17f99ab223f42eec58523fa89a49f243efba754b",
      "parents": [
        "307730acd9d271bc4c3d44f2dfed0eab67e1657d"
      ],
      "author": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Tue Oct 13 11:03:03 2015 +1100"
      },
      "committer": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Fri Nov 27 15:36:04 2015 +1100"
      },
      "message": "Namespace XTRACE commands\n\nI noticed this when debugging some grenade issues failures.\n\nAn include of grenade/functions stores the current value of XTRACE\n(on) and disables xtrace for the rest of the import.\n\nWe then include devstack\u0027s \"functions\" library, which now overwrites\nthe stored value of XTRACE the current state; i.e. disabled.\n\nWhen it finishes it restores the prior state (disabled), and then\ngrenade restores the same value of XTRACE (disabled).\n\nThe result is that xtrace is incorrectly disabled until the next time\nit just happens to be turned on.\n\nThe solution is to name-space the store of the current-value of xtrace\nso when we finish sourcing a file, we always restore the tracing value\nto what it was when we entered.\n\nSome files had already discovered this.  In general there is\ninconsistency around the setting of the variable, and a lot of obvious\ncopy-paste.  This brings consistency across all files by using\n_XTRACE_* prefixes for the sotre/restore of tracing values.\n\nChange-Id: Iba7739eada5711d9c269cb4127fa712e9f961695\n"
    },
    {
      "commit": "925c256cd45bd845c8dd03827ae9c26f43ad5481",
      "tree": "76032e9f47087780c0cf1e1bd06d1a293d2bdd98",
      "parents": [
        "ca802bcfcc1d45697da9f4c26683d2887eb63f39"
      ],
      "author": {
        "name": "Matt Riedemann",
        "email": "mriedem@us.ibm.com",
        "time": "Tue Aug 25 13:40:25 2015 -0700"
      },
      "committer": {
        "name": "Matt Riedemann",
        "email": "mriedem@us.ibm.com",
        "time": "Tue Aug 25 13:40:25 2015 -0700"
      },
      "message": "Remove NOVA_VIF_DRIVER variable\n\nCommit 7561c8ded211d53e8745d1420a73b82bd0fc35cf removed the\nlibvirt.vif_driver option from Nova in Juno so we should remove the\nvariable from devstack since it\u0027s useless / confusing.\n\nChange-Id: I70a8cb4a3606eb5eabd3c0ef331945e72c80543a\n"
    },
    {
      "commit": "e263c82e48a431e502bd6baceb6dfcfdc1750cbb",
      "tree": "5ca592e668dedb4debc6c7170f3abf37cc4bc0c6",
      "parents": [
        "2f8e08b5728f4272b415b1c0aab8ff62eae29b06"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Fri Dec 05 14:25:28 2014 -0500"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Wed Dec 10 11:28:05 2014 -0500"
      },
      "message": "add shebang lines to all lib files\n\nWith gerrit 2.8, and the new change screen, this will trigger syntax\nhighlighting in gerrit. Thus making reviewing code a lot nicer.\n\nChange-Id: Id238748417ffab53e02d59413dba66f61e724383\n"
    },
    {
      "commit": "a12dee433c12c336d804ebe36a6a36f7d3c85f65",
      "tree": "6cd96e880f4e2337d6b3b1e2e0cad3f882331eca",
      "parents": [
        "0986a7b760e34741d4df6f97851f6d98fec4f99c"
      ],
      "author": {
        "name": "sailajay",
        "email": "y.sailaja@gmail.com",
        "time": "Thu Nov 06 16:14:32 2014 -0800"
      },
      "committer": {
        "name": "sailajay",
        "email": "y.sailaja@gmail.com",
        "time": "Fri Nov 07 00:23:09 2014 +0000"
      },
      "message": "Devstack Nuage Plugin correct the ovs_bridge parameter\n\nThis commit fixes the name of ovs_bridge parameter and the section it is set in nova.conf by the nuage plugin\n\nCloses-Bug: 1390256\n\nChange-Id: I63c929e827db10d0cf5450907a273d880fc757f6\n"
    },
    {
      "commit": "0fc1cc29ac5d9aa88e47611de72f3a98f14bf242",
      "tree": "e9029982bf4c45ac62e3d355b9dded459d15e357",
      "parents": [
        "df2cc34db60454e33aa2974509faa24b6d7093d4"
      ],
      "author": {
        "name": "Henry Gessau",
        "email": "gessau@cisco.com",
        "time": "Sun Jul 06 22:54:34 2014 -0400"
      },
      "committer": {
        "name": "Henry Gessau",
        "email": "gessau@cisco.com",
        "time": "Tue Jul 15 21:29:29 2014 -0400"
      },
      "message": "Use one name for neutron database after healing\n\nNow that the Neutron database is healed we no longer need a\nplugin-specific name for it.\n\nRelated Blueprint: db-migration-refactor\n\nChange-Id: If25e77444f115817e5570bb447bde5b9c8d6e686\n"
    },
    {
      "commit": "e3a9160c0d6c7802141fb147339ab12f76482c85",
      "tree": "87c1c831cf248211a583676bff47d612283d917a",
      "parents": [
        "4c0e728780d49bfca80b147676ad1b96d16e24e4"
      ],
      "author": {
        "name": "Dean Troyer",
        "email": "dtroyer@gmail.com",
        "time": "Fri Mar 28 12:40:56 2014 -0500"
      },
      "committer": {
        "name": "Dean Troyer",
        "email": "dtroyer@gmail.com",
        "time": "Fri Mar 28 12:40:59 2014 -0500"
      },
      "message": "Fix Neutron plugin XTRACE handling\n\nThe various Neutron plugin files need to have unique variables for the\nxtrace state as they are sometimes nested more than two levels deep\nand MY_XTRACE is getting stomped.  This gives each of the neutron_plugin\nand neutron_thirdparty include files a unique XTRACE state variable.\n\nI don\u0027t think this is a problem with any of the other plugin include\nfiles (yet) so this just handles Neutron for now.\n\nChange-Id: I7c272a48e7974edecaff5f431ff7443dd6622588\n"
    },
    {
      "commit": "ae1728917373986b68d2b0abe2e7052fb78e5903",
      "tree": "072fd801b22306b41d152ca6a695a053acb143d0",
      "parents": [
        "9db04f7f30012e5d685d10d350c765ee0ce3f00e"
      ],
      "author": {
        "name": "ronak",
        "email": "ronak.malav.shah@gmail.com",
        "time": "Tue Mar 04 15:48:22 2014 -0800"
      },
      "committer": {
        "name": "ronak",
        "email": "ronak.malav.shah@gmail.com",
        "time": "Tue Mar 04 20:43:05 2014 -0800"
      },
      "message": "Supporting Nuage Networks\u0027 Plugin through devstack\n\nNuage networks\u0027 plugin specific configuration setting file for devstack\n\nChange-Id: I936f87b8fbc6f90130514b2fc0d111eab861da7c\nImplements: blueprint nuage-networks-plugin\n"
    }
  ]
}