)]}'
{
  "commit": "6b9c60b06d04bc519195fca1f621b10accfeb46b",
  "tree": "33d6498495269b38f8a4f57351beb0101aee2dda",
  "parents": [
    "cc8c07895df8b34ad339b457f07a2e3724215d79"
  ],
  "author": {
    "name": "Erik Språng",
    "email": "sprang@webrtc.org",
    "time": "Sun May 10 12:29:03 2020"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Mon May 11 09:14:37 2020"
  },
  "message": "Removes lock release in PacedSender callback.\n\nThe PacedSender currently has logic to temporarily release its internal\nlock while sending or asking for padding.\nThis creates some tricky situations in the pacing controller where we\nneed to consider if some thread can enter while we the process thread is\nactually processing, just temporarily busy sending.\n\nSince the pacing call stack is no longer cyclic, we can actually remove\nthis lock-release now.\n\nBug: webrtc:10809\nChange-Id: Ic59c605252bed1f96a03406c908a30cd1012f995\nReviewed-on: https://webrtc-review.googlesource.com/c/src/+/173592\nReviewed-by: Sebastian Jansson \u003csrte@webrtc.org\u003e\nCommit-Queue: Erik Språng \u003csprang@webrtc.org\u003e\nCr-Commit-Position: refs/heads/master@{#31206}\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cd298f9b0bff69e5699178d0e2aef232744258bf",
      "old_mode": 33188,
      "old_path": "modules/pacing/paced_sender.cc",
      "new_id": "1d02fe95e4cfeb87ccf13989426913a2816df9a8",
      "new_mode": 33188,
      "new_path": "modules/pacing/paced_sender.cc"
    },
    {
      "type": "modify",
      "old_id": "818480b18b5ec1d10805b870bd9d76ae7382cdf6",
      "old_mode": 33188,
      "old_path": "test/direct_transport.cc",
      "new_id": "f4ae047870d5e74d3a56b1a310f3a883842e0e77",
      "new_mode": 33188,
      "new_path": "test/direct_transport.cc"
    }
  ]
}