)]}'
{
  "log": [
    {
      "commit": "8cd310d7638843f07f4c88adaf3aed9db7668073",
      "tree": "14ea21f0f52c2804940f15e6ac0f479a33f79cf1",
      "parents": [
        "ac042d41222eea83bf360b4db89c4c7bf415457d"
      ],
      "author": {
        "name": "Eric Fried",
        "email": "efried@us.ibm.com",
        "time": "Tue May 16 13:52:03 2017 -0500"
      },
      "committer": {
        "name": "Eric Fried",
        "email": "efried@us.ibm.com",
        "time": "Tue May 16 14:56:57 2017 -0500"
      },
      "message": "Restore log colors under devstack/systemd\n\nOne of the pending issues with the conversion to systemd was the loss of\nlog coloring.  It turns out that journalctl by default strips out\ncharacters it considers \"unprintable\" - including the color codes\nemitted by the old-style logging.  However, journalctl can be made to\nprint them by adding the `-a` flag.\n\nThis change makes devstack\u0027s log formatter conf settings include color\ncodes like the old screen-based setup used to\n\nWe also remove stackrc\u0027s setting of JOURNALCTL_F, whose usage was\nremoved via I6af6d1857effaf662a9d72bd394864934eacbe70.\n\nChange-Id: I2401e267913a24d18dae355aa933072dbbdab1d8\n"
    },
    {
      "commit": "8b8441f3becbae2e704932569bff384dcc5c6713",
      "tree": "6b3d89020924bcd9158e8f1138b38ddd3ec14546",
      "parents": [
        "803acffcf9254e328426ad67380a99f4f5b164ec"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Tue May 02 06:14:11 2017 -0400"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Tue May 02 06:44:22 2017 -0400"
      },
      "message": "Default developer use case to systemd\n\nThis moves the developer use case over to systemd, and updates all the\nrelevant docs to discuss the systemd workflow instead of screen. It\ndoes so by defaulting USE_SCREEN\u003dFalse, so will not impact people that\nset it explicitly.\n\nChange-Id: I6d664612bc2b850eb7f56852afbc841867223ab7\n"
    },
    {
      "commit": "def07b21f86ee70cae223785f0195c91de1f2b64",
      "tree": "88420a5ee4cb887dd5d8354769f0d8574f23a603",
      "parents": [
        "d356b31b507e47f70f474adce302dd5d2cc6e499"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Thu Mar 30 07:18:49 2017 -0400"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Thu Mar 30 07:18:49 2017 -0400"
      },
      "message": "Updated docs from finding more things about systemd\n\nChange-Id: I3d807cd342f30eada04a6be2af7db482f9c4a796\n"
    },
    {
      "commit": "5edae54855b6b9af4283cef07e0b0d1a0f90cd3e",
      "tree": "38a1c4516ffc6f472f455363fac5bd24c5b65425",
      "parents": [
        "fb73a8fc6fa8cdc826b10c47490bc47cd0e6776a"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Tue Mar 21 20:50:24 2017 -0400"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Tue Mar 28 07:19:15 2017 -0400"
      },
      "message": "initial work to enable systemd service running\n\nDuring the PTG there was a discussion that the screen developer\nworkflow wasn\u0027t nearly as useful as it once was. There were now too\nmany services to see them all on one screen, and one of the most\ncommon service restart scenarios was not restarting one service, but a\nbunch to get code to take effect.\n\nThis implements a 3rd way of running services instead of direct\nforking via bash, or running under screen, which is running as systemd\nunits.\n\nLogging is adjusted because it\u0027s redundant to log datetime in oslo.log\nwhen journald has that.\n\nSwift needed to have services launched by absolute path to work.\n\nThis is disabled by default, but with instructions on using it. The\nlong term intent is to make this the way to run devstack, which would\nbe the same between both the gate and local use.\n\nSome changes were also needed to run_process to pass the run User\nin. A hack around the keystone uwsgi launcher was done at the same\ntime to remove a run_process feature that only keystone uwsgi uses.\n\nChange-Id: I836bf27c4cfdc449628aa7641fb96a5489d5d4e7\n"
    }
  ]
}