Google Git
Sign in
chromium / chromium / src / d1f52e8fcdd8a79210d90f24ee4f057a0c31e09f
commitd1f52e8fcdd8a79210d90f24ee4f057a0c31e09f[log] [tgz]
authorMarcello Salomao <msalomao@google.com>Thu May 18 00:08:04 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 18 00:08:04 2023
tree4e9097e5e2a4070eabc7b4791ac487405744cdf2
parent2c4a316697591c6b53d7885738b075db33be22ee [diff]
Revert "[MirrorSync] Use ProgressEvents for Inline Sync Status"

This reverts commit 707fbba26560541c262599cc245fa03832542e87.

Reason for revert: DriveFS side changes won't be ready on time

Original change's description:
> [MirrorSync] Use ProgressEvents for Inline Sync Status
>
> For a discussion of the benefits of replacing Inline Sync
> Status' source of truth from SyncStatus with ProgressItem
> events, please refer to:
>
> docs/document/d/13oggvoaJv5TB1eCK-zeiYaj-JZoe7HmCngh7ZEtcmRM?resourcekey=0-oOV0wT5fbg4cr6LIokPmVA#heading=h.tkbbez5uuf0m
>
> Associated review cl/519926630.
>
> Bug: b:274038292
> Test: chromeos_unittests *DriveFsHostTest*
> Test: browser_tests DriveSpecific/FilesAppBrowserTest.Test/driveInlineSyncStatusParentFolder*
> Change-Id: I27638fe912e8b5e65a7bccdcd12a1381484457de
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4383127
> Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
> Commit-Queue: Marcello Salomao <msalomao@google.com>
> Reviewed-by: Ben Reich <benreich@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1142551}

Bug: b:274038292
Change-Id: Ie63177efb61c550bb4409864fb866c1d1b35b788
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4541905
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Luciano Pacheco <lucmult@chromium.org>
Owners-Override: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1145721}
17 files changed
tree: 4e9097e5e2a4070eabc7b4791ac487405744cdf2
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.