)]}'
{
  "commit": "86152436eb06a76e495425c1aa862833576fbc71",
  "tree": "8bed12785c8a67a91c12fd19f43a02ee090a4764",
  "parents": [
    "e4d50d47a9eb15f42bdd561803a29a4d7c3eb8ec"
  ],
  "author": {
    "name": "Peter Lieven",
    "email": "pl@kamp.de",
    "time": "Fri Sep 05 22:07:41 2014 +0200"
  },
  "committer": {
    "name": "Gerd Hoffmann",
    "email": "kraxel@redhat.com",
    "time": "Wed Sep 17 15:14:41 2014 +0200"
  },
  "message": "ui/vnc: set TCP_NODELAY\n\nwe currently have the Nagle algorithm enabled for all outgoing VNC updates.\nThis may delay sensitive updates as mouse movements or typing in the console.\nAs we currently prepare all data in a buffer and then send as much as we can\ndisabling the Nagle algorithm should not cause big trouble. Well established\nVNC servers like TightVNC set TCP_NODELAY as well.\nA regular framebuffer update request generates exactly one framebuffer update\nwhich should be pushed out as fast as possible.\n\nSigned-off-by: Peter Lieven \u003cpl@kamp.de\u003e\nSigned-off-by: Gerd Hoffmann \u003ckraxel@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f8d9b7db9571e04cf4fd361853ac205f470f4be2",
      "old_mode": 33188,
      "old_path": "ui/vnc.c",
      "new_id": "0fe6eff1b8a661d7cb123b37bb49921c72d5df16",
      "new_mode": 33188,
      "new_path": "ui/vnc.c"
    }
  ]
}