)]}'
{
  "commit": "43b1d8ad30bcd61c8cc62fce52fdc6d8381e5732",
  "tree": "35cd178d25795958207b0d59a4a7d676d95f89df",
  "parents": [
    "c33305c5dd4cc06e71eb0c66a7150aa6ab647c99"
  ],
  "author": {
    "name": "Steve Block",
    "email": "steveblock@google.com",
    "time": "Thu Feb 16 17:49:31 2012 +0000"
  },
  "committer": {
    "name": "Steve Block",
    "email": "steveblock@google.com",
    "time": "Wed Feb 22 17:21:43 2012 +0000"
  },
  "message": "Drop support for Android HTTP stack\n\nAll future releases will use the Chromium HTTP stack and maintaining two HTTP\n    stacks adds maintenance overhead. The Chromium HTTP stack requires V8, but we\n    now use V8 in all build targets (b/5495373), so we can safely drop the Android\n    HTTP stack.\n\nLoadListener, HttpAuthHandlerImpl, Network, SslErrorHandlerImpl, WebViewWorker\n- Android-stack specific, removed\nStreamLoader, FrameLoader\n- Require LoadListener, removed\nCacheLoader, ContentLoader, DataLoader, FileLoader\n- Extend StreamLoader, removed\n\nBrowserFrame\n- Removed methods that create LoadListener\n- BrowserFrame.startLoadingResource() is called from native\nCallbackProxy, WebView\n- Removed calls to Network methods\nCacheManager, CookieManager, CookieSyncManager, WebViewCore, WebResourceResponse\n- Removed other Android-stack specific code\nJniUtlil\n- Removed useChromiumHttpStack()\nWebViewDatabase\n- Removed all code to create cookies and cache databases for Android HTTP stack\n\nSee corresponding WebKit change https://android-git.corp.google.com/g/166327.\n\nBug: 5495616\nChange-Id: If491675516f6eb187077af4220214bb6e6a8d045\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3f9ba47e1345f356bdaeaaf5f260897075eec662",
      "old_mode": 33188,
      "old_path": "media/libstagefright/Android.mk",
      "new_id": "1524cbeef5369de9dbdedccf950d7a3fa1dab308",
      "new_mode": 33188,
      "new_path": "media/libstagefright/Android.mk"
    }
  ]
}