)]}'
{
  "log": [
    {
      "commit": "5b5fa8b412312a41cfd4d7ab475b54d4f730ed2a",
      "tree": "30cecc0c704bc9b0ecafd4de5034d92a9e239822",
      "parents": [
        "e9ae98c24f115d9ff041953e705a95ef330355ce"
      ],
      "author": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Thu Oct 06 15:40:49 2016 -0700"
      },
      "committer": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Thu Oct 06 19:06:05 2016 -0700"
      },
      "message": "Add {Get,Set}CohortHint interface.\n\nExport the \"cohort hint\" getter and setter in the client interfaces\n(D-Bus and Binder). The cohort hint is sent to Omaha on every update\ncheck request but can be ignored and/or reset by Omaha on every\nresponse.\n\nOther minor linter fixes to the affected files.\n\nBug: 31740109\nTest: Build with D-Bus and with Binder.\n\nChange-Id: I93214f6ffb8662c238b3351e52bf2bdf23e46a9c\n"
    },
    {
      "commit": "b3fa53bf760bd0a6fd1ef9df28cb425586d733f6",
      "tree": "457141d09742613dd2b3f64a92d6da4a83a0e390",
      "parents": [
        "ed9bd92e00099eddda86b32fd2bb4896cb44cd51"
      ],
      "author": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Mon Apr 18 19:57:58 2016 -0700"
      },
      "committer": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Tue May 03 17:17:58 2016 -0700"
      },
      "message": "Parse and expose end-of-life flag.\n\nOmaha update or noupdate response can include _key\u003dvalue pairs with\narbitrary data. One of those key can be \"_eol\" with the one of the\nvalues \"supported\", \"security-only\" or \"eol\" which notifies the device\nthe end-of-life status of the device with respect to updates. This\ninformation is now exposed via GetEolStatus() to the client so it\ncan be properly displayed in the UI.\n\nBug: 27924505\nTEST\u003dAdded unittest. Run `update_engine_client --eol_status` on link.\n\nChange-Id: Icc15f25b4d0b19cc894f5afc52ac7c43c7818982\n"
    },
    {
      "commit": "2997173235e88c5e4cb13d2844f74afc7b25d6e2",
      "tree": "1efea76748ffcb44c7340c8cae9d9cbfb51cc19e",
      "parents": [
        "64d9878470aa7b388e971862181daf6260851602"
      ],
      "author": {
        "name": "Shuqian Zhao",
        "email": "shuqianz@google.com",
        "time": "Fri Feb 05 11:29:32 2016 -0800"
      },
      "committer": {
        "name": "Charlene Zhao",
        "email": "shuqianz@google.com",
        "time": "Wed Feb 10 22:38:45 2016 +0000"
      },
      "message": "Add a feature to get the last UpdateAttempt ErrorCode from update_engine\n\nFor autotest, update_engine test failures are always hard to debug,\nsince the error message is not clear. Add a new flag \u0027last_attempt_error\u0027\nto get the last UpdateAttempt ErrorCode from update_engine.\n\nBug:25598547\nTest:emerge-peppy update_engine\n     emerge-peppy update_engine_client\n     cros flash a test image to DUT.\n     (on the DUT):update_engine_client --last_attempt_error\n     Compare the results with the update_engine logs, matched.\n\nChange-Id: Id12681097ed30b0826cad68809f17f934a07e5b2\n"
    },
    {
      "commit": "cbea78f22e1420f3cd2167b963acbf599941eb84",
      "tree": "e9b92314469978a7765f6e2d93aead0b238e13ca",
      "parents": [
        "4d2990d04917bd8140772bee63f2cf43837b6a30"
      ],
      "author": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Tue Sep 15 22:59:56 2015 -0700"
      },
      "committer": {
        "name": "Alex Deymo",
        "email": "deymo@google.com",
        "time": "Tue Sep 15 23:08:34 2015 -0700"
      },
      "message": "Remove obsolete GetKernelDevices() method.\n\nupdate_engine daemon exposed a DBus method GetKernelDevices() returning\nthe list of available kernel block devices and whether they were\nbootable or not. This method was a developer-only method, since it\ncan\u0027t be called from chrome, and no other daemon uses it, besides the\nupdate_engine_client.\n\nThe update_engine daemon moved from managing root and kernel partitions\nexplicitly, to manage slots. So the notion of which block device is the\n\"kernel\" device is now unknown. The information about the available\nslots and their status, can be managed with the external tool bootctl\ninstead. Therefore, this patch removes the GetKernelDevices() method.\n\nBug: None\nTest: emerge-link update_engine; `mma` on AOSP.\n\nChange-Id: I715bdbb73ebbbca3dfb381b16043224a170a3832\n"
    },
    {
      "commit": "2bddadd17e31ca1341604f8652432a8619557688",
      "tree": "226f7f40cdef3863aff282cb6180c149ca0787dd",
      "parents": [
        "9a423ff19e3a7503cd8128998b3a10d65c499fdc"
      ],
      "author": {
        "name": "Alex Vakulenko",
        "email": "avakulenko@chromium.org",
        "time": "Thu Mar 27 13:23:46 2014 -0700"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Fri Mar 28 23:11:38 2014 +0000"
      },
      "message": "update_engine: Added more logging and debugging for rollback checking\n\nTo help troubleshoot issues similar to http://crbug.com/356975 I added\nmore logging in DBus methods of update_engine to trace various stages\nof determining available boot partitions, etc.\n\nAlso added two more DBus methods - to get the suggested rollback\npartition name (and switched CanRollback to use this method) and\nthe list of availavle kernel partitions along with the \u0027bootable\u0027\nflag for each.\n\nChanged update_engine_client to show the name of avaiable rollback\npartition with --can_rollback and also added --show_kernels to\noutput list of available kernel partitions and whether each partition\nis bootable or not.\n\nBUG\u003dNone\nTEST\u003dUnit tests pass\n\nChange-Id: Ib7f92a6460c578953ea1ba9b23bd0669acb0e22f\nReviewed-on: https://chromium-review.googlesource.com/191949\nReviewed-by: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\nTested-by: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\nCommit-Queue: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\n"
    },
    {
      "commit": "dea2eac2c565ed5b587278b865e2c07b805a8333",
      "tree": "87501bf70fdff62b273011aad7ca2e91e052652c",
      "parents": [
        "759c275760b51defcfe5545abb887ad2616335f4"
      ],
      "author": {
        "name": "Alex Vakulenko",
        "email": "avakulenko@chromium.org",
        "time": "Fri Mar 14 15:56:59 2014 -0700"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Thu Mar 20 23:51:59 2014 +0000"
      },
      "message": "update_engine: Added ability to retrieve old version via DBus\n\nNow it is possible to retrieve an old OS version that was in use\nbefore the last reboot, provided that we are now booted into\nan updated version. This is to be used by crash reporter in case\nthe reboot was caused by a crash in kernel while reboot was pending\nfor an update. In such a scenario, the crash would be attributed\nto the current (updated) version, which is wrong.\n\nAlso added additional parameter, --old_version, to\nupdate_engine_client to retrieve the old version number, if any,\nfrom the update engine.\n\nBUG\u003dchrome-os-partner:26518\nTEST\u003dcros deploy and tested via update_engine_client\n\nChange-Id: I84e2322c5698b44b4c77f25c8f4211cdb367e5dc\nReviewed-on: https://chromium-review.googlesource.com/190149\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\nCommit-Queue: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\n"
    },
    {
      "commit": "59e253e555072d11f3646fc1286459cbc6aa5419",
      "tree": "720e3cde0cb4c1c235f04c776db6ce730ad525ff",
      "parents": [
        "55f39b7043fae6b7c27188d0cd797946098b42ef"
      ],
      "author": {
        "name": "Alex Vakulenko",
        "email": "avakulenko@chromium.org",
        "time": "Mon Feb 24 10:40:21 2014 -0800"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Tue Feb 25 22:12:31 2014 +0000"
      },
      "message": "update_engine: added CanRollback dbus method\n\nAdded a method to the update engine to check if a rollback\npartition is available and can be booted from.\nupdate_engine_client is also updated to call the function\nwhen --can_rollback paramater is specified\n\nBUG\u003dchromium:343301\nTEST\u003dRan \"update_engine_client --can_rollback\" and unit tests\n\nChange-Id: If3fcb29a0067069a22812f60e9b67c6fdbbd18bd\nReviewed-on: https://chromium-review.googlesource.com/187157\nTested-by: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nCommit-Queue: Alex Vakulenko \u003cavakulenko@chromium.org\u003e\n"
    },
    {
      "commit": "8c75ea9f2bc9c42d6ce30abb4b93a2930a5d4bce",
      "tree": "76b54b6d2ef26484302727597a2b661a843abd03",
      "parents": [
        "fa40450ea1ac5f9f835c6a0823ecb36d7dd09876"
      ],
      "author": {
        "name": "Daniel Erat",
        "email": "derat@chromium.org",
        "time": "Fri Jan 10 10:16:07 2014 -0800"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Sat Jan 11 17:43:41 2014 +0000"
      },
      "message": "update_engine: Let \"power\" user query update status.\n\nChange update_engine\u0027s D-Bus configuration to allow the\n\"power\" user (used by powerd) to query the update status.\npowerd already listens for signals announcing update state\nchanges, but it also ought to query the current status if it\ngets restarted for some reason.\n\nIt also removes some \"deny\" directives that are apparently\nundesirable, as \"deny\" is already the default (see\nhttp://crbug.com/219054).\n\nBUG\u003dnone\nTEST\u003dconfirmed that powerd is able to query the update\n     status after being restarted\n\nChange-Id: I60389a20409c2534e5e306bb7662b424f1d272c3\nReviewed-on: https://chromium-review.googlesource.com/182243\nTested-by: Daniel Erat \u003cderat@chromium.org\u003e\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nCommit-Queue: Daniel Erat \u003cderat@chromium.org\u003e\n"
    },
    {
      "commit": "3c55abd5fa1e3db40974b2e8d94f2ddce65fe40d",
      "tree": "b601a42e18c7871b980cae929fcd66647d4cf4e7",
      "parents": [
        "c7dd853f695619ebf6dea15831a21aac1a23f209"
      ],
      "author": {
        "name": "David Zeuthen",
        "email": "zeuthen@chromium.org",
        "time": "Mon Oct 14 12:48:03 2013 -0700"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Fri Nov 01 19:11:38 2013 +0000"
      },
      "message": "Add D-Bus method to get the duration since an update completed.\n\nThis new API can be used by Chrome to automatically reboot the device\nat N hours after updating. This is implemented as a D-Bus method that\nreturns the number of micro-seconds on the wall-clock since the update\ncompleted. If the device has not updated, the D-Bus method returns an\nerror.\n\nFor robustness, durations are measured using the CLOCK_BOOTTIME clock\ninstead of the usual CLOCK_REALTIME clock. This avoids interference\nwith NTP adjustments, the RTC clock being wrong and other things.\n\nBUG\u003dchromium:218192\nTEST\u003dNew unit test + unit tests pass + manual test on a device using\n    the gdbus(1) command as the chronos user.\n\nChange-Id: I51d44d69afe2d3024bb0780916c3c4e3f8ebb19e\nReviewed-on: https://chromium-review.googlesource.com/173032\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nCommit-Queue: David Zeuthen \u003czeuthen@chromium.org\u003e\nTested-by: David Zeuthen \u003czeuthen@chromium.org\u003e\n"
    },
    {
      "commit": "75a4c3ee6d45c0892e33e46973816e2fec07e277",
      "tree": "fc687614e9b9bcd1ad831638c25abdfe99d3aacf",
      "parents": [
        "20f005c62b55471d3ed8f6fd55e23564adeb59fe"
      ],
      "author": {
        "name": "David Zeuthen",
        "email": "zeuthen@chromium.org",
        "time": "Fri Sep 06 11:36:59 2013 -0700"
      },
      "committer": {
        "name": "chrome-internal-fetch",
        "email": "chrome-internal-fetch@google.com",
        "time": "Sat Sep 07 23:03:42 2013 +0000"
      },
      "message": "update_engine_client: Add -interactive\u003dtrue|false flag\n\nThis makes it easier to test the update_engine codepaths dealing with\nnon-interactive update attempts.\n\nBUG\u003dchromium:273251\nTEST\u003dManually tested with \u0027update_engine_client -update -interactive\u003dX\u0027 +\n    unit tests pass.\n\nChange-Id: Id3894261fd1c0dc2afdf2426484835f487924433\nReviewed-on: https://chromium-review.googlesource.com/168445\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nCommit-Queue: David Zeuthen \u003czeuthen@chromium.org\u003e\n"
    },
    {
      "commit": "5fdf776fe7eabb0492636ae52d4809ebdbe8a25e",
      "tree": "8e5d63a43243b70d2c65e45074fbebaf5c735a4d",
      "parents": [
        "d5b3e427e14817266da4d6ead89815778dedf089"
      ],
      "author": {
        "name": "Alex Deymo",
        "email": "deymo@chromium.org",
        "time": "Wed Jul 17 20:01:40 2013 -0700"
      },
      "committer": {
        "name": "Caroline Tice",
        "email": "cmtice@chromium.org",
        "time": "Thu Aug 29 23:09:43 2013 +0000"
      },
      "message": "New DBus methods to enable/disable P2P update sharing.\n\nThis patch adds two new methods to enable/disable sharing updates\nover P2P in the local network. This allows a crosh command to set\nand get this flag to enable or disable this feature.\n\nBUG\u003dchromium:260441\nTEST\u003dManual test. See below.\n\nManual test procedure.\n1. Enable P2P:\nupdate_engine_client -p2p_update yes -show_p2p_update\n\n[0829/141039:INFO:update_engine_client.cc(433)] Current update using P2P setting: ENABLED\n[0829/141039:INFO:update_engine_client.cc(500)] Done.\n\n2. Start the p2p server (this will be done by the p2p_manager\n   as part of the update_engine procedure).\n\n3. Run an update check\nupdate_engine_client -check_for_update\n\nThe /var/log/update_engine.log shows the following line confirming\np2p is enabled.\n[0829/141317:INFO:p2p_manager.cc(194)] Returning value 1 for whether p2p is enabled.\n\n4. Disable p2p and verify the p2p server is not running.\nupdate_engine_client -p2p_update no -show_p2p_update\n\n[0829/141039:INFO:update_engine_client.cc(433)] Current update using P2P setting: ENABLED\n[0829/141039:INFO:update_engine_client.cc(500)] Done.\n\n5. Verify p2p server is not running (ps aux | grep p2p doesn\u0027t show\np2p-server)\n\nChange-Id: I3215e2961be440c491f669d4c580bbf87f7fec25\nReviewed-on: https://chromium-review.googlesource.com/62505\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nCommit-Queue: Alejandro Deymo \u003cdeymo@chromium.org\u003e\nTested-by: Alejandro Deymo \u003cdeymo@chromium.org\u003e\n"
    },
    {
      "commit": "cb7fa886480e74440b41e94856cd3d12a6099e00",
      "tree": "77784cab5c6dc597b745788f12095dd824c9361d",
      "parents": [
        "049d16529de8d43c7c61ae5677efc570d0976a22"
      ],
      "author": {
        "name": "Chris Sosa",
        "email": "sosa@chromium.org",
        "time": "Thu Jul 25 17:02:59 2013 -0700"
      },
      "committer": {
        "name": "ChromeBot",
        "email": "chrome-bot@google.com",
        "time": "Mon Aug 05 14:29:46 2013 -0700"
      },
      "message": "Remove all mentions of Set/Get Track and hard-coding of canary-channel.\n\nThis CL removes the deprecated functionality of Set/Get Track previously\nused to change channels. Now that the UI is using Set/Get Channel we no\nlonger need these methods. I\u0027ve also gone ahead and fixed the long standing\nbug of needed to do an update check before testing channel change.\n\nI\u0027ve also added the testing of allow powerwash functionality to update_engine\nclient to better test this feature.\n\nBUG\u003dchromium:221850\nTEST\u003dunittests + update_engine_client with channel change and allowing\npowerwash and not allowing powerwash. Confirmed the versions were as expected (\nwhen going more stable we send version 0.0.0.0 when we allow powerwash vs the\nactual version when not).\n\nChange-Id: I87297f7e7e103bb25e62f2d896e155e758030ead\nReviewed-on: https://gerrit.chromium.org/gerrit/63674\nCommit-Queue: Chris Sosa \u003csosa@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Chris Sosa \u003csosa@chromium.org\u003e\n"
    },
    {
      "commit": "f4867c4dab4d1ca566f1aa3f585bd16d87b911dd",
      "tree": "2e98607aafd4d60331e97a3bd578dea5d9e02ab7",
      "parents": [
        "820cc706c5ef60a3be96f5487f616bfed2b1d207"
      ],
      "author": {
        "name": "Alex Deymo",
        "email": "deymo@chromium.org",
        "time": "Fri Jun 28 14:41:39 2013 -0700"
      },
      "committer": {
        "name": "ChromeBot",
        "email": "chrome-bot@google.com",
        "time": "Tue Jul 09 15:21:24 2013 -0700"
      },
      "message": "Add DBus methods to allow/disallow updates over 3G\n\nThis fix adds a new DBus pair of methods to allow/disallow the\nupdates over cellular networks and get the current state of this\nsetting. The setting is overridden by the device policy and the\nSetUpdateOverCellularPermission() method fails if called on an\nenrolled device that has the autoupdate settings in the device\npolicy.\n\nBUG\u003dchromium:213401\nTEST\u003dunittests for connection_manager changes. Manual test for the DBus service, see below.\n\nManual test procedure.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nRun on a shell:\n\n1. Test for the default setting.\n$ update_engine_client -show_update_over_cellular\n[0701/183633:INFO:update_engine_client.cc(371)] Current update over cellular network setting: DISABLED\n[0701/183633:INFO:update_engine_client.cc(443)] Done.\n\n2. Test that enable works.\n$ update_engine_client -update_over_cellular\u003dyes -show_update_over_cellular\n[0701/183655:INFO:update_engine_client.cc(371)] Current update over cellular network setting: ENABLED\n[0701/183655:INFO:update_engine_client.cc(443)] Done.\n\n3. Test that disable works.\n$ update_engine_client -update_over_cellular\u003dno -show_update_over_cellular\n[0701/183659:INFO:update_engine_client.cc(371)] Current update over cellular network setting: DISABLED\n[0701/183659:INFO:update_engine_client.cc(443)] Done.\n\n4. Enable again the update over cellular, connect the chromebook to a 3G\nand perform an update check.\n\nChange-Id: Ic234a3ef8898b1e60e26277208276a958b7e0d94\nReviewed-on: https://gerrit.chromium.org/gerrit/60716\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Alex Deymo \u003cdeymo@chromium.org\u003e\nTested-by: Alex Deymo \u003cdeymo@chromium.org\u003e\n"
    },
    {
      "commit": "86dc54dc5ea1abf27eb49b08f4f7dd40f8184099",
      "tree": "395c7d195a048b7eb85e28591d69608eb84229a6",
      "parents": [
        "3b74843840fda8e6954986bdd6a9fccc835d5580"
      ],
      "author": {
        "name": "Yuri Gorshenin",
        "email": "ygorshenin@chromium.org",
        "time": "Thu Jun 20 17:53:36 2013 +0400"
      },
      "committer": {
        "name": "ChromeBot",
        "email": "chrome-bot@google.com",
        "time": "Mon Jun 24 14:03:59 2013 -0700"
      },
      "message": "Added permissions to call {Get|Set}Channel.\n\nAdded permissions to call {Get|Set}Channel.\n\nBUG\u003dchromium:219292\nTEST\u003dnone\n\nChange-Id: Ie23109602d2981f05f9508cc147b3b47b3df13a3\nReviewed-on: https://gerrit.chromium.org/gerrit/59422\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Yuri Gorshenin \u003cygorshenin@chromium.org\u003e\nReviewed-by: Yuri Gorshenin \u003cygorshenin@chromium.org\u003e\nCommit-Queue: Yuri Gorshenin \u003cygorshenin@chromium.org\u003e\n"
    },
    {
      "commit": "d317e40be46e1b69f624a8165472c99fe6346a1e",
      "tree": "6edd17f9f184c55409eb4563c01c138ab155c8a5",
      "parents": [
        "c41c228da3e34d04fb556f56a4815c51ce741ff6"
      ],
      "author": {
        "name": "Chris Sosa",
        "email": "sosa@chromium.org",
        "time": "Wed Jun 12 13:47:09 2013 -0700"
      },
      "committer": {
        "name": "ChromeBot",
        "email": "chrome-bot@google.com",
        "time": "Tue Jun 18 16:11:46 2013 -0700"
      },
      "message": "Implement Rollback to previously booted partitions.\n\nThis CL implements rollback to whatever partition we ran from before.\nWe expose this functionality via dbus under AttemptRollback and expose\na new command-line option to update_engine_client that a developer can\nuse.\n\nBUG\u003dchromium:242665\nTEST\u003dUnittests, full update, update + rollback and verified.\n\nChange-Id: Ie59f90b9a0b777dc1329592449090c70892236bf\nReviewed-on: https://gerrit.chromium.org/gerrit/58427\nCommit-Queue: Chris Sosa \u003csosa@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Chris Sosa \u003csosa@chromium.org\u003e\n"
    },
    {
      "commit": "c1ba09a8f4d3eda4654b34bf01d41fd9ad1d9f38",
      "tree": "fe37b90ede427fb8e8b849ac7f35072457d2eac9",
      "parents": [
        "21be0753ca991afed45998ecd4c157c245f1fad0"
      ],
      "author": {
        "name": "Jay Srinivasan",
        "email": "jaysri@chromium.org",
        "time": "Tue Aug 14 14:15:57 2012 -0700"
      },
      "committer": {
        "name": "Gerrit",
        "email": "chrome-bot@google.com",
        "time": "Tue Aug 14 16:11:50 2012 -0700"
      },
      "message": "Support in update_engine for script for UI jank investigation.\n\nWe need to update image_to_live.sh to run in a loop to help investigate\nthe kernel behavior during AU. Since update_engine doesn\u0027t allow a\nnew update to be applied unless the device is rebooted after the previous\nupdate, this CL adds an option to reset the state for testing purposes.\n\nThis CL does not cause any change in product code, since\nupdate_engine_client will never be invoked with this option in product.\n\nBUG\u003dchromium-os:27954\nTEST\u003dTested on ZGB.\nChange-Id: I561e58893818a1b4990fdc131cd3bb64e473155e\nReviewed-on: https://gerrit.chromium.org/gerrit/29907\nCommit-Ready: Jay Srinivasan \u003cjaysri@chromium.org\u003e\nReviewed-by: Jay Srinivasan \u003cjaysri@chromium.org\u003e\nTested-by: Jay Srinivasan \u003cjaysri@chromium.org\u003e\n"
    },
    {
      "commit": "000d895da247697f4e4e0c67a3a847f71fca8eb9",
      "tree": "e1d152c444fed693649bd748ee1df1ffc7d7dc98",
      "parents": [
        "abc7bc0f5d88f110b463191bb8384f95d3c4230a"
      ],
      "author": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Wed Mar 02 15:21:14 2011 -0800"
      },
      "committer": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Wed Mar 02 15:21:14 2011 -0800"
      },
      "message": "AU: Full proxy support\n\nThis CL Introduces a new proxy resolver that queries Chrome browser\nfor all URLs. This means the updater now works with Proxy\nAutoConfiguration (PAC) files and automatic proxy detection.\n\nBUG\u003dchromium-os:9478\nTEST\u003dperformed update, unittests\n\nReview URL: http://codereview.chromium.org/6594025\n\nChange-Id: I2c169aec06109e3eabc4011e0b536685dfd13f79\n"
    },
    {
      "commit": "583667b33cb62b97fbbd792d6c830c530d759ec1",
      "tree": "923655017e09d3d7307c3a9bc6097e62c3c0ccee",
      "parents": [
        "34e41a1b50ccd06f5b3dad7a1ab1d467c7e8e00e"
      ],
      "author": {
        "name": "Satoru Takabayashi",
        "email": "satorux@chromium.org",
        "time": "Wed Oct 27 13:09:57 2010 +0900"
      },
      "committer": {
        "name": "Satoru Takabayashi",
        "email": "satorux@chromium.org",
        "time": "Wed Oct 27 13:09:57 2010 +0900"
      },
      "message": "AU: Implement getting of tracks through GetTrack.\n\nAdd SetTrack and GetTrack to UpdateEngine.xml as well.\n\nBUG\u003dchromium-os:8104\nTEST\u003dtested on device with update_engine_client\n\nChange-Id: I10ef2552e9280524b3a8d5f232d104a81a114e06\n\nReview URL: http://codereview.chromium.org/4181001\n"
    },
    {
      "commit": "0aa39a6ac40e52d783e3d80abe59ffe30ec7c1dd",
      "tree": "dd278292149750d2c024b46c942efff2ae4487ab",
      "parents": [
        "58529db65ee21eaa3279bc2bb28baf1fec72e621"
      ],
      "author": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Fri Aug 13 12:41:57 2010 -0700"
      },
      "committer": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Fri Aug 13 12:41:57 2010 -0700"
      },
      "message": "Remove obsolete CheckForUpdate/check_for_update D-Bus method.\n\nBUG\u003d5402\nTEST\u003dunit tests, gmerged on device and tried updates, emerged libcros.\n\nChange-Id: I94ac031a33e6ca586a67974235496d245ded04bd\n\nReview URL: http://codereview.chromium.org/3179014\n"
    },
    {
      "commit": "296889c68c92b04d307035c5803681f8d2c8f9d3",
      "tree": "12bc939be362b65145d45efa26d5886a5d5e80dc",
      "parents": [
        "192ced474a4226f1921fcdaa6a763f5f2d7e1b49"
      ],
      "author": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Fri Jul 23 16:20:54 2010 -0700"
      },
      "committer": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Fri Jul 23 16:20:54 2010 -0700"
      },
      "message": "AU: Provide a reboot_if_needed D-Bus API.\n\nThis will reboot if the current state is UPDATED_REBOOT_NEEDED.\nAlso add -reboot option to the update_engine_client.\n\nBUG\u003d4250\nTEST\u003dunit tests,gmerged on device and tried reboot requests\n\nReview URL: http://codereview.chromium.org/3034026\n"
    },
    {
      "commit": "5a7f565a542196f24eb87ddac96508f8a84e3329",
      "tree": "139f0837dc61973ae806c76185a7533a0d78d804",
      "parents": [
        "777dbfae01be95ac66f385cd96dc6e4b421fefe5"
      ],
      "author": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Thu Jul 22 21:40:09 2010 -0700"
      },
      "committer": {
        "name": "Darin Petkov",
        "email": "petkov@chromium.org",
        "time": "Thu Jul 22 21:40:09 2010 -0700"
      },
      "message": "Add support to update_engine_client for -app_version and -omaha_url.\n\nThese options prevent auto-detection of these parameters.\nNote that this CL makes the check_for_update DBus method obsolete from\nthe client\u0027s point of view.\n\nBUG\u003d4593\nTEST\u003dunit tests, gmerged on device and tried the client with different options.\n\nReview URL: http://codereview.chromium.org/3048008\n"
    },
    {
      "commit": "63b96d74b2ffe5999243ab5c33f588030bcb42ce",
      "tree": "4a6e93710964a383ea862a91a944b086d745452b",
      "parents": [
        "f98bff879c8e90840582f6a60a93918465f2d8b9"
      ],
      "author": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Mon May 10 13:08:54 2010 -0700"
      },
      "committer": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Mon May 10 13:08:54 2010 -0700"
      },
      "message": "AU: DBus support.\n\nA few changes to support dbus in the Update Engine daemon:\n\n- SConstruct: build marshaller for the dbus signal.\n\n- Update Attempter: respond to dbus calls and broadcast status on dbus\n  signal.\n\n- Update Engine Client: flag to listen for status updates.\n\n- Also, cleanup outdated code in Omaha Response Handler.\n\nBUG\u003dNone\nTEST\u003dattached unittests/on device tests\n\nReview URL: http://codereview.chromium.org/2037002\n"
    },
    {
      "commit": "4e9b9f4d57a0c95fb1b9281077f0eef5fdf5e345",
      "tree": "32bd273a8369718b300bba4af4532580f6090bb4",
      "parents": [
        "09e56d64202d2148b95008c5bd18cf719ec0f40c"
      ],
      "author": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Mon Apr 26 15:06:43 2010 -0700"
      },
      "committer": {
        "name": "Andrew de los Reyes",
        "email": "adlr@chromium.org",
        "time": "Mon Apr 26 15:06:43 2010 -0700"
      },
      "message": "AU: Beginnings of dbus support.\n\nThe AU will be a daemon that runs as root. Non-root will communicate\nvia dbus with the updater to do things such as: query status, request\nforced or full updates, etc.\n\nNew files for dbus:\n\nUpdateEngine.conf - security configuration\ndbus_constants.h - common constants\ndbus_service.* - The object exposed over dbus\norg.chromium.UpdateEngine.service - the dbus service file\nudpate_attempter.* - Refactored this out of main.cc\nupdate_engine_client.cc - Simple command line utility to interact with\nUpdate Engine over dbus. Whereas Update Engine runs as root, this tool\nruns as non-root user.\n\nReview URL: http://codereview.chromium.org/1733013\n"
    }
  ]
}