)]}'
{
  "commit": "cfd2fbc4e3223afd79ed32fdfbdf09fa7ddfa43b",
  "tree": "27f1e2a57caeba35bf4030a371323a75be3fd413",
  "parents": [
    "0d05e48371c67ce0e95faf0915e96b97361770f5"
  ],
  "author": {
    "name": "Philip P. Moltmann",
    "email": "moltmann@google.com",
    "time": "Fri Feb 08 13:07:57 2019 -0800"
  },
  "committer": {
    "name": "Philip P. Moltmann",
    "email": "moltmann@google.com",
    "time": "Sat Feb 16 12:11:38 2019 -0800"
  },
  "message": "Make PermissionControllerManager user aware\n\nMost of the commands of PermissionControllerManager should go to the\ncalling user. If not - and the alternate user is running - we should\nuse the recommended way to talk to alternate users. This recommended way\nis to create a package context for the user and call the method on this\nnew context.\n\nHence\n- At a time we can have more than one RemoteService (one per user)\n- Connect to the user declared in Context#getUser instead of the calling\nuser\n\nTest: Called methods on work-profiles and saw alternate\nPermissionController apps to be spawned.\nChange-Id: I9ed87db1f658f18b69d19b39ba9f96361ec5af82\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "addfe3da39b3e97ce93f833cf6a8ba1c09fa0097",
      "old_mode": 33188,
      "old_path": "core/java/android/permission/PermissionControllerManager.java",
      "new_id": "d62bc6c5a87254deb41d0d5387ec2db8d30bdfa0",
      "new_mode": 33188,
      "new_path": "core/java/android/permission/PermissionControllerManager.java"
    }
  ]
}
