)]}'
{
  "commit": "e9e984de2b2b4d820cc6b1f7eebee2f18a42643b",
  "tree": "585d95407be67e20c13024c0db16fe1ac7b4ffb0",
  "parents": [
    "99fa7cbeeced9c2f5d5c00b9b9f4164f63e3ff0c"
  ],
  "author": {
    "name": "srgnk",
    "email": "sergey.n.nemov@gmail.com",
    "time": "Fri May 17 22:21:31 2019 +0200"
  },
  "committer": {
    "name": "Bruce A. Mah",
    "email": "bmah@es.net",
    "time": "Fri May 17 13:21:31 2019 -0700"
  },
  "message": "fix: Pass repeating_payload option to server (#867)\n\nIf client was started with --repeating-payload option, tell the\r\nserver to use the repeating_payload also.\r\n\r\nSince repeating_payload is a client specific option at the moment and\r\nwe don\u0027t tell the server if repeating_payload was set not not,\r\nserver always uses randomized patterns in reverse and bidirectional\r\nmodes disregarding what patterns the client was told to generate.\r\n\r\nSo, if client was started with both --repeating-payload and --reverse,\r\nthe server would still send the randomized data to the client which\r\ndoesn\u0027t seem right.\r\n\r\nThis commit fixes this issue.\r\n\r\nSigned-off-by: Sergey Nemov \u003csergey.nemov@intel.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4c1d927df0bca0b25e37455f7e5a06dc34115919",
      "old_mode": 33261,
      "old_path": "src/iperf_api.c",
      "new_id": "7e169ba9e5bdd6a487bd4c7ac34126cefff8315c",
      "new_mode": 33261,
      "new_path": "src/iperf_api.c"
    }
  ]
}