)]}'
{
  "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": "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": "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": "aee18c749b0e3a1a3a6907a33db76ae83b8d41d9",
      "tree": "01a8ab5abb9867986f3e848918abd9e749b691cd",
      "parents": [
        "0ed4af02da0bd4a0f757dd8c2156913e6c7a724c"
      ],
      "author": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Fri Feb 21 15:35:08 2014 +1100"
      },
      "committer": {
        "name": "Ian Wienand",
        "email": "iwienand@redhat.com",
        "time": "Fri Feb 28 07:59:03 2014 +1100"
      },
      "message": "Enforce function declaration format in bash8\n\nCheck that function calls look like ^function foo {$ in bash8, and fix\nall existing failures of that check.  Add a note to HACKING.rst\n\nChange-Id: Ic19eecb39e0b20273d1bcd551a42fe400d54e938\n"
    },
    {
      "commit": "16dd8b3ed94d5cd217d22a26c18dca52bfca115e",
      "tree": "62994b309b39fc5d4920808f506e763feb3b6f07",
      "parents": [
        "e38cad092ff96dc0178a19fe6f33f13db99eebb0"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean.dague@samsung.com",
        "time": "Mon Feb 03 09:10:54 2014 +0900"
      },
      "committer": {
        "name": "Chmouel Boudjnah",
        "email": "chmouel@enovance.com",
        "time": "Wed Feb 05 07:52:54 2014 +0100"
      },
      "message": "introduce if/then \u0026 for/do rules\n\nwe mostly have a consistent style on if/then \u0026 for/do in devstack,\nexcept when we don\u0027t. This attempts to build a set of rules to\nenforce this.\n\nBecause there are times when lines are legitimately long, and there\nis a continuation, this starts off ignoring if and for loops with\ncontinuations. But for short versions, we should enforce this.\n\nChanges to make devstack pass are included. The fact that the\ncleanup patch was so small is pretty solid reason that this is\nactually the style we\u0027ve all agreed to.\n\nPart of a git stash from hong kong that I finally cleaned up.\n\nChange-Id: I6376d7afd59cc5ebba9ed69e5ee784a3d5934a10\n"
    },
    {
      "commit": "ef1e08022b9553b07757005e7a5103fbdc0d99f0",
      "tree": "1a082ee2a6fee770cba93f7ae218db597be1ae23",
      "parents": [
        "b200b1d4dda4e60bacd921f98e4e47d5b4f046d9"
      ],
      "author": {
        "name": "armando-migliaccio",
        "email": "armamig@gmail.com",
        "time": "Thu Jan 02 16:33:53 2014 -0800"
      },
      "committer": {
        "name": "armando-migliaccio",
        "email": "armamig@gmail.com",
        "time": "Tue Jan 14 08:14:25 2014 -0800"
      },
      "message": "Add sanity check framework to verify neutron server/backend integration\n\nSome Neutron plugins require controllers and multiple backend services\nto operate correctly. This patch adds the framework for third party\nplugins to run sanity checks after Neutron Server has started.\n\nThis simple addition may reveal potential configuration pitfalls\nmuch earlier in the dev/test cycle, thus speeding up the build\nchurn process.\n\nThe first plugin that uses this framework is the VMware NSX one.\n\nCloses-bug: #1265671\n\nChange-Id: I17f9c5c8e828316ff03f0eff42ae4ae6c6c58733\n"
    },
    {
      "commit": "b05c876994183b6a1d53dfbdcea2ca4a7743035f",
      "tree": "e5361481fe1ea3f96da5c9139034530bb35706a7",
      "parents": [
        "0a03806e281d1f197e54d48318e4a7bba3eab77c"
      ],
      "author": {
        "name": "Mark McClain",
        "email": "mark.mcclain@dreamhost.com",
        "time": "Sat Jul 06 23:29:39 2013 -0400"
      },
      "committer": {
        "name": "Mark McClain",
        "email": "mark.mcclain@dreamhost.com",
        "time": "Sun Jul 07 00:15:11 2013 -0400"
      },
      "message": "update for name change to Neutron\n\nNote: Nova and Horizon are not updated until those projects have\nmigrated.\n\nChange-Id: I256ef20e7caadd9c96e6dd908c5d8b69ca5c4aeb\n"
    },
    {
      "commit": "614202fc40923a60f83d7108ea66ce07846de324",
      "tree": "a369dfc064c208b9da46acc22e2a1abfeba347fa",
      "parents": [
        "7640350bb5b343fae0932c86b7e536bb5d5e8db1"
      ],
      "author": {
        "name": "JordanP",
        "email": "jordan.pittier@gmail.com",
        "time": "Thu May 16 11:16:13 2013 +0200"
      },
      "committer": {
        "name": "JordanP",
        "email": "jordan.pittier@gmail.com",
        "time": "Wed May 22 10:00:30 2013 +0200"
      },
      "message": "On unstack : clean up network namespaces created by quantum\n\nAlso removes OVS ports\n\nFix Bug #1156837\n\nChange-Id: Id4178c0a12a3ada76403a57a736a9c7a908d6a4a\n"
    },
    {
      "commit": "8d55be31a95043236d52ee891bacae5ea9f5ed37",
      "tree": "8b71dba39b5b461eaa2cca893e96d622b34e9d58",
      "parents": [
        "f127e2f316f1161bacdf4cccdbc3e56b2b8a54a8"
      ],
      "author": {
        "name": "Dean Troyer",
        "email": "dtroyer@gmail.com",
        "time": "Thu Feb 07 17:16:35 2013 -0600"
      },
      "committer": {
        "name": "Dean Troyer",
        "email": "dtroyer@gmail.com",
        "time": "Thu Feb 07 17:16:40 2013 -0600"
      },
      "message": "Handle nested xtrace states (Quantum edition)\n\nThe lib/quantum_* directories include plugin files that also\ncontains the $XTRACE bits at entry and exit.  The nested XTRACE handling overwrote\nthe value from lib/quantum.  So...make the nested files use their own\nXTRACE variables.\n\nChange-Id: Ib5e643371666b21402eef2ec58bfb1dfb7e1ccc4\n"
    },
    {
      "commit": "0dd34df455637ee29176525974d6dab93f530e66",
      "tree": "c3dd87d2965008ddd5dac92431a3b5b564c08c8c",
      "parents": [
        "e575b6f9ae6ab530c27cb5b2f680025d7078c4ea"
      ],
      "author": {
        "name": "Isaku Yamahata",
        "email": "yamahata@valinux.co.jp",
        "time": "Fri Dec 28 13:15:31 2012 +0900"
      },
      "committer": {
        "name": "Isaku Yamahata",
        "email": "yamahata@valinux.co.jp",
        "time": "Mon Jan 21 11:33:24 2013 +0900"
      },
      "message": "lib/quantum: refactor quantum plugins and third party\n\nAs quantum plugin support is coming like floodlight, nvp and nec,\nit\u0027s worth while to refactor quantum plugin logic so that each plugin can\nbe modified/enhanced intervening with other quantum plugin.\nAnd new plugin support can be added easily (hopefully) without modifying\ncore logic.\n\nChange-Id: Ic5ab5b993272fdd3b4e779823323777a845ee681\n"
    },
    {
      "commit": "4b26d3191ee82e96fedaffa68362919deb8a3813",
      "tree": "9d90fafb61c198b658d54acc8995bc0ac35c27ad",
      "parents": [
        "eae8f82678aa5ba70cb136e93bc1234671f1cbcc"
      ],
      "author": {
        "name": "Sumit Naiksatam",
        "email": "sumitnaiksatam@gmail.com",
        "time": "Fri Jan 04 10:32:54 2013 -0800"
      },
      "committer": {
        "name": "Sumit Naiksatam",
        "email": "sumitnaiksatam@gmail.com",
        "time": "Sat Jan 12 01:04:57 2013 -0800"
      },
      "message": "Quantum FloodLight/BigSwitch Plugin Support\n\nThe patch introduces devstack support for the Quantum FloodLight/BigSwitch\nRESTProxy Plugin.\n\nChange-Id: I8c032fd16723ed6055821de0860fae508df371b7\nImplements: blueprint quantum-floodlight-bigswitch-plugin-support\n"
    }
  ]
}