)]}'
{
  "log": [
    {
      "commit": "ec7bc11c3103d9310568a391271be52baef273a7",
      "tree": "c7d69b3c47c8ff86876cd662b4ace630c1e1362b",
      "parents": [
        "24e1d72aa2a1024417121b0d91bf9a6f3b883a96"
      ],
      "author": {
        "name": "Amin Hassani",
        "email": "ahassani@chromium.org",
        "time": "Thu Oct 29 16:47:58 2020 -0700"
      },
      "committer": {
        "name": "Commit Bot",
        "email": "commit-bot@chromium.org",
        "time": "Tue Nov 03 03:19:41 2020 +0000"
      },
      "message": "update_engine: Create cros vs. aosp boundary clear\n\nIts time to make the boundary between Chrome OS and Android code more\nclear. This CL moves all CrOS only code to \"chromeos\" directory and the\nsame for Android (in \"android\" directory). This way we would easily know\nwhich code is uses in which project and can keep the code cleaner and\nmore maintainable.\n\nOne big remaining problem is download_action* files. It seems like\nDownloadAction class does a lot of things that chrome OS needs and it\ndepends on a lot of Chrome OS stuff, but Android is also using thie\nAction in a way that circumvent the Chrome OS stuff. For example Android\nchecks for SystemState to be nullptr to not do things. This is really\nfragile and needs to change. Probably Android Team has to implement\ntheir own DownloadAction of some sort and not re use the Chrome OS one\nin a very fragile way.\n\nRemoved a few android files that have not been used anywhere.\n\nChanged some clang-format and lint issues in order to pass preupload.\n\nBUG\u003db:171829801\nTEST\u003dcros_workon_make --board reef --test update_engine\n\nChange-Id: I3fff1d4a100a065a5c1484a845241b5521614d9f\nReviewed-on: https://chromium-review.googlesource.com/c/aosp/platform/system/update_engine/+/2508965\nTested-by: Amin Hassani \u003cahassani@chromium.org\u003e\nAuto-Submit: Amin Hassani \u003cahassani@chromium.org\u003e\nReviewed-by: Jae Hoon Kim \u003ckimjae@chromium.org\u003e\nReviewed-by: Tianjie Xu \u003cxunchang@google.com\u003e\nReviewed-by: Kelvin Zhang \u003czhangkelvin@google.com\u003e\nCommit-Queue: Amin Hassani \u003cahassani@chromium.org\u003e\n"
    },
    {
      "commit": "2562cf2960c97acdaac2dee7e306cd3c88cd9c68",
      "tree": "7c45b7d14abd6710b55aa01240f51c7fa04f1bdf",
      "parents": [
        "2b291f05765486899cf0b4e8eda83bc89f083271"
      ],
      "author": {
        "name": "Yifan Hong",
        "email": "elsk@google.com",
        "time": "Tue Jul 21 19:28:44 2020 -0700"
      },
      "committer": {
        "name": "Yifan Hong",
        "email": "elsk@google.com",
        "time": "Tue Aug 04 19:06:06 2020 +0000"
      },
      "message": "Add binder_service_stable_android\n\nAdd a new binder service that uses the exact same service delegate as\nits implementation, but exposes itself with the IUpdateEngineStable* APIs.\n\nNote: Even though the new interface requires only one binding at a time,\nrace conditions for different clients are NOT handled in this CL.\nMultiple binding is still possible via the unstable IUpdateEngine API\nand via the Java android.os.UpdateEngine interface. Moreover, bindings\nwith bind(IUpdateEngineStableCallback) and bind(IUpdateEngineCallback)\nare handled separately.\n\nTest: unit test\nBug: 160996544\n\nChange-Id: I26e8b4a58c0243d46ffcd7354d04f0c69f8fa66f\n"
    },
    {
      "commit": "565331e3db3cca0746535a4f06dbf4de50032c5f",
      "tree": "1224346209a4b1076e8c7ae465f80c292477b277",
      "parents": [
        "c80d2d8867d9ef659b5bdad5b66f77f58a1af2e4"
      ],
      "author": {
        "name": "Amin Hassani",
        "email": "ahassani@chromium.org",
        "time": "Mon Jun 24 14:11:29 2019 -0700"
      },
      "committer": {
        "name": "chrome-bot",
        "email": "chrome-bot@chromium.org",
        "time": "Fri Jun 28 21:50:21 2019 -0700"
      },
      "message": "update_engine: Break UpdateEngineDaemon into their own implementations\n\nIt looks like Android and ChromeOS have completely different\nimplementation of the daemon. So instead of polluting the source with\nUSE_* flags, just break it into their own implementation files. At the\nvery least this allows deprecating USE_BINDER and USE_OMAHA flag\ncompletely.\n\nBUG\u003dchromium:978672\nTEST\u003dunittest, cros flash two times.\n\nChange-Id: Ia5c4f9274e275a2c1ba9334111b694514914a475\nReviewed-on: https://chromium-review.googlesource.com/1674583\nTested-by: Amin Hassani \u003cahassani@chromium.org\u003e\nCommit-Ready: Amin Hassani \u003cahassani@chromium.org\u003e\nLegacy-Commit-Queue: Commit Bot \u003ccommit-bot@chromium.org\u003e\nReviewed-by: Amin Hassani \u003cahassani@chromium.org\u003e\n"
    }
  ]
}