commit | d1500dc291cdbb267be7d4ec81aadbfbe6fd8184 | [log] [tgz] |
---|---|---|
author | Qijiang Fan <fqj@google.com> | Fri Jul 31 06:28:32 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jul 31 06:28:32 2020 +0000 |
tree | 611b2271f6945e73ec471e7b7aa17635a5c6f32b | |
parent | 3f77e5de3367b740d11b7cb12540f8e7a03a82c6 [diff] | |
parent | 19de62cd2ad6009b63ed5d260a74e70f986d281d [diff] |
Merge commit '7a65c6bc48c96fa640cbf13d45a692d0a64200e3' into HEAD am: e07960d51b am: 35d33c2abd am: 876093a455 am: 19de62cd2a Original change: https://android-review.googlesource.com/c/platform/external/libbrillo/+/1371779 Change-Id: Id1ebed94ab42f55a3a57f9093d4bd39013768c3b
libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.
This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.
To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/
This allows AOSP to cherry pick or merge changes directly back into their fork.