commit | 35d33c2abd0f6b51d7569afc119cb0a85c430dba | [log] [tgz] |
---|---|---|
author | Qijiang Fan <fqj@google.com> | Fri Jul 31 05:26:11 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jul 31 05:26:11 2020 +0000 |
tree | 611b2271f6945e73ec471e7b7aa17635a5c6f32b | |
parent | afba1ee7ecdcfae7e93337e2d955d580b0a48f31 [diff] | |
parent | e07960d51bc791a977d8b5020684f342723aa8c2 [diff] |
Merge commit '7a65c6bc48c96fa640cbf13d45a692d0a64200e3' into HEAD am: e07960d51b Original change: https://android-review.googlesource.com/c/platform/external/libbrillo/+/1371779 Change-Id: I6c5edc0de99e3374f3ab21a97180f38f194afdd1
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.